mirrors/qemu
0
0
Fork 0
mirror of https://github.com/qemu/qemu.git synced 2024-11-27 22:03:35 +08:00
Code Issues Packages Projects Releases Wiki Activity

doc/memory.txt: correct description of MemoryRegionOps fields

Browse Source 
Probably what happened was that when the API was being designed it
started off with an 'aligned' field, and then later the field name
and semantics were changed but the docs weren't updated to match.

Similarly, cpu_register_io_memory() does not exist anymore, so
clarify the documentation for .old_mmio.

Reported-by: Cao jin <caoj.fnst@cn.fujitsu.com>
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
This commit is contained in:
Peter Maydell 2016-02-26 16:40:51 +08:00 committed by Paolo Bonzini
parent 8210f5f6f5
commit ef00bdaf8c
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/memory.txt
View File

@ -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 - .valid.min_access_size, .valid.max_access_size define the access sizes
(in bytes) which the device accepts; accesses outside this range will (in bytes) which the device accepts; accesses outside this range will
have device and bus specific behaviour (ignored, or machine check) have device and bus specific behaviour (ignored, or machine check)
- .valid.aligned specifies that the device only accepts naturally aligned - .valid.unaligned specifies that the *device being modelled* supports
accesses. Unaligned accesses invoke device and bus specific behaviour. 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 - .impl.min_access_size, .impl.max_access_size define the access sizes
(in bytes) supported by the *implementation*; other access sizes will be (in bytes) supported by the *implementation*; other access sizes will be
emulated using the ones available. For example a 4-byte write will be emulated using the ones available. For example a 4-byte write will be
@ -306,5 +307,5 @@ various constraints can be supplied to control how these callbacks are called:
- .impl.unaligned specifies that the *implementation* supports unaligned - .impl.unaligned specifies that the *implementation* supports unaligned
accesses; if false, unaligned accesses will be emulated by two aligned accesses; if false, unaligned accesses will be emulated by two aligned
accesses. accesses.
- .old_mmio can be used to ease porting from code using - .old_mmio eases the porting of code that was formerly using
cpu_register_io_memory(). It should not be used in new code. cpu_register_io_memory(). It should not be used in new code.