mirror of
https://github.com/yuzu-emu/unicorn.git
synced 2024-12-23 00:05:36 +00:00
docs/devel/memory.txt: Document _with_attrs accessors
When we added the _with_attrs accessors we forgot to mention them in the documentation. Backports commit 687ac05d71bbb3172e0546248e40483ef43a4813 from qemu
This commit is contained in:
parent
01683fe97e
commit
a0a846a5d7
|
@ -273,8 +273,15 @@ is made visible (which can be immediately, later, or never).
|
||||||
MMIO Operations
|
MMIO Operations
|
||||||
---------------
|
---------------
|
||||||
|
|
||||||
MMIO regions are provided with ->read() and ->write() callbacks; in addition
|
MMIO regions are provided with ->read() and ->write() callbacks,
|
||||||
various constraints can be supplied to control how these callbacks are called:
|
which are sufficient for most devices. Some devices change behaviour
|
||||||
|
based on the attributes used for the memory transaction, or need
|
||||||
|
to be able to respond that the access should provoke a bus error
|
||||||
|
rather than completing successfully; those devices can use the
|
||||||
|
->read_with_attrs() and ->write_with_attrs() callbacks instead.
|
||||||
|
|
||||||
|
In addition 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
|
||||||
|
|
Loading…
Reference in a new issue