[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-trivial] [PATCH v2] doc/memory.txt: fix typo

From: Cao jin
Subject: [Qemu-trivial] [PATCH v2] doc/memory.txt: fix typo
Date: Fri, 26 Feb 2016 18:59:03 +0800

and also modify its description, make the text parallel to the existing
.impl.unaligned doc.

bonus: slightly modified the diagram, make it prettier.
Signed-off-by: Cao jin <address@hidden>
 docs/memory.txt | 19 ++++++++++---------
 1 file changed, 10 insertions(+), 9 deletions(-)

diff --git a/docs/memory.txt b/docs/memory.txt
index 8745f76..8aee3d6 100644
--- a/docs/memory.txt
+++ b/docs/memory.txt
@@ -186,15 +186,15 @@ of its own subregions: D of size 0x1000 at offset 0 and E 
of size 0x1000 at
 offset 0x2000. As a diagram:
         0      1000   2000   3000   4000   5000   6000   7000    8000
-        |------|------|------|------|------|------|------|-------|
+        |------|------|------|------|------|------|------|------|
   A:    [                                                       ]
-  B:                  [                          ]
-  D:                  [DDDDD]
-  E:                                [EEEEE]
+  B:                  [                           ]
+  D:                  [DDDDDD]
+  E:                                [EEEEEE]
 The regions that will be seen within this address range then are:
 Since B has higher priority than C, its subregions appear in the flat map
 even where they overlap with C. In ranges where B has not mapped anything
@@ -203,7 +203,7 @@ C's region appears.
 If B had provided its own MMIO operations (ie it was not a pure container)
 then these would be used for any addresses in its range not handled by
 D or E, and the result would be:
 Priority values are local to a container, because the priorities of two
 regions are only compared when they are both children of the same container.
@@ -297,8 +297,9 @@ various constraints can be supplied to control how these 
callbacks are called:
  - .valid.min_access_size, .valid.max_access_size define the access sizes
    (in bytes) which the device accepts; accesses outside this range will
    have device and bus specific behaviour (ignored, or machine check)
- - .valid.aligned specifies that the device only accepts naturally aligned
-   accesses.  Unaligned accesses invoke device and bus specific behaviour.
+ - .valid.unaligned specifies that the *device being modelled* supports
+   unaligned accesses; If false, unaligned accesses will invoke the appropriate
+   bus or CPU specific behaviour.
  - .impl.min_access_size, .impl.max_access_size define the access sizes
    (in bytes) supported by the *implementation*; other access sizes will be
    emulated using the ones available.  For example a 4-byte write will be

reply via email to

[Prev in Thread] Current Thread [Next in Thread]