| commit | 79cc6cdb932a5cf1a1ee05f6de12a7d102818d21 | [log] [tgz] |
|---|---|---|
| author | Oliver Upton <oliver.upton@linux.dev> | Mon Oct 07 23:30:28 2024 +0000 |
| committer | Marc Zyngier <maz@kernel.org> | Tue Oct 08 10:40:27 2024 +0100 |
| tree | f41d3cb833f797542ad4e6d1e245f682ce3a1fc6 | |
| 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 <oliver.upton@linux.dev> Link: https://lore.kernel.org/r/20241007233028.2236133-5-oliver.upton@linux.dev Signed-off-by: Marc Zyngier <maz@kernel.org>