diff options
| author | Oliver Upton <[email protected]> | 2024-10-07 23:30:28 +0000 |
|---|---|---|
| committer | Marc Zyngier <[email protected]> | 2024-10-08 10:40:27 +0100 |
| commit | 79cc6cdb932a5cf1a1ee05f6de12a7d102818d21 (patch) | |
| tree | f41d3cb833f797542ad4e6d1e245f682ce3a1fc6 /scripts/gdb/linux/stackdepot.py | |
| parent | c268f204f7c5784e84583c1c44d427bac09f517a (diff) | |
KVM: arm64: nv: Clarify safety of allowing TLBI unmaps to reschedule
There's been a decent amount of attention around unmaps of nested MMUs,
and TLBI handling is no exception to this. Add a comment clarifying why
it is safe to reschedule during a TLBI unmap, even without a reference
on the MMU in progress.
Signed-off-by: Oliver Upton <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Marc Zyngier <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/stackdepot.py')
0 files changed, 0 insertions, 0 deletions