summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSebastian Huber <sebastian.huber@embedded-brains.de>2020-02-11 07:24:22 +0100
committerSebastian Huber <sebastian.huber@embedded-brains.de>2020-02-11 07:27:04 +0100
commit0cdd4823fc05429ae834a18d8fca67594b249775 (patch)
tree1db91a534a5268f5a01c5d83487d13596e28bbf3
parentd45c51a95e401b6d20b4483eebf4c0d601d95f51 (diff)
downloadrtems-docs-0cdd4823fc05429ae834a18d8fca67594b249775.tar.bz2
c-user: Clarify CONFIGURE_DIRTY_MEMORY
Update #3843.
-rw-r--r--c-user/configuring_a_system.rst5
1 files changed, 3 insertions, 2 deletions
diff --git a/c-user/configuring_a_system.rst b/c-user/configuring_a_system.rst
index 00584c1..a013d45 100644
--- a/c-user/configuring_a_system.rst
+++ b/c-user/configuring_a_system.rst
@@ -452,8 +452,9 @@ DESCRIPTION:
Otherwise, they are not.
NOTES:
- Dirtying memory can add significantly to system boot time. It may assist
- in finding code that assumes memory starts set to zero. In case
+ Dirtying memory can add significantly to system boot time. It may assist in
+ finding code that incorrectly assumes the content of free memory areas is
+ cleared to zero during system initialization. In case
:ref:`CONFIGURE_ZERO_WORKSPACE_AUTOMATICALLY` is also defined, then the
memory is first dirtied and then zeroed.