[rtems-docs commit] c-user: Clarify CONFIGURE_DIRTY_MEMORY
Sebastian Huber
sebh at rtems.org
Tue Feb 11 06:27:15 UTC 2020
Module: rtems-docs
Branch: master
Commit: 0cdd4823fc05429ae834a18d8fca67594b249775
Changeset: http://git.rtems.org/rtems-docs/commit/?id=0cdd4823fc05429ae834a18d8fca67594b249775
Author: Sebastian Huber <sebastian.huber at embedded-brains.de>
Date: Tue Feb 11 07:24:22 2020 +0100
c-user: Clarify CONFIGURE_DIRTY_MEMORY
Update #3843.
---
c-user/configuring_a_system.rst | 5 +++--
1 file 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.
More information about the vc
mailing list