mirror of
https://github.com/Motorhead1991/qemu.git
synced 2025-08-02 07:13:54 -06:00
include/exec/memop.h: Expand comment for MO_ATOM_SUBALIGN
Expand the example in the comment documenting MO_ATOM_SUBALIGN, to be clearer about the atomicity guarantees it represents. Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Reviewed-by: Richard Henderson <richard.henderson@linaro.org> Message-id: 20250228103222.1838913-1-peter.maydell@linaro.org
This commit is contained in:
parent
02ae315467
commit
84e5ce68c0
1 changed files with 6 additions and 2 deletions
|
@ -91,8 +91,12 @@ typedef enum MemOp {
|
|||
* Depending on alignment, one or both will be single-copy atomic.
|
||||
* This is the atomicity e.g. of Arm FEAT_LSE2 LDP.
|
||||
* MO_ATOM_SUBALIGN: the operation is single-copy atomic by parts
|
||||
* by the alignment. E.g. if the address is 0 mod 4, then each
|
||||
* 4-byte subobject is single-copy atomic.
|
||||
* by the alignment. E.g. if an 8-byte value is accessed at an
|
||||
* address which is 0 mod 8, then the whole 8-byte access is
|
||||
* single-copy atomic; otherwise, if it is accessed at 0 mod 4
|
||||
* then each 4-byte subobject is single-copy atomic; otherwise
|
||||
* if it is accessed at 0 mod 2 then the four 2-byte subobjects
|
||||
* are single-copy atomic.
|
||||
* This is the atomicity e.g. of IBM Power.
|
||||
* MO_ATOM_NONE: the operation has no atomicity requirements.
|
||||
*
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue