diff options
| author | Kirill A. Shutemov <[email protected]> | 2023-03-12 14:25:57 +0300 |
|---|---|---|
| committer | Dave Hansen <[email protected]> | 2023-03-16 13:08:39 -0700 |
| commit | 5ef495e55f07aa117fdd8e187c9901cefc02fe0a (patch) | |
| tree | 796fe02adece943b5b149acbd00f9d327a821596 /scripts/gdb | |
| parent | b19b74bc99b1501a550f4448d04d59b946dc617a (diff) | |
x86: Allow atomic MM_CONTEXT flags setting
So far there's no need in atomic setting of MM context flags in
mm_context_t::flags. The flags set early in exec and never change
after that.
LAM enabling requires atomic flag setting. The upcoming flag
MM_CONTEXT_FORCE_TAGGED_SVA can be set much later in the process
lifetime where multiple threads exist.
Convert the field to unsigned long and do MM_CONTEXT_* accesses with
__set_bit() and test_bit().
No functional changes.
Signed-off-by: Kirill A. Shutemov <[email protected]>
Signed-off-by: Dave Hansen <[email protected]>
Acked-by: Peter Zijlstra (Intel) <[email protected]>
Tested-by: Alexander Potapenko <[email protected]>
Link: https://lore.kernel.org/all/20230312112612.31869-3-kirill.shutemov%40linux.intel.com
Diffstat (limited to 'scripts/gdb')
0 files changed, 0 insertions, 0 deletions