projects / linux-2.6-microblaze.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: c268f20) | patch
KVM: arm64: nv: Clarify safety of allowing TLBI unmaps to reschedule
authorOliver Upton <oliver.upton@linux.dev>
Mon, 7 Oct 2024 23:30:28 +0000 (23:30 +0000)
committerMarc Zyngier <maz@kernel.org>
Tue, 8 Oct 2024 09:40:27 +0000 (10:40 +0100)
commit79cc6cdb932a5cf1a1ee05f6de12a7d102818d21
treef41d3cb833f797542ad4e6d1e245f682ce3a1fc6tree
parentc268f204f7c5784e84583c1c44d427bac09f517acommit | 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>
arch/arm64/kvm/sys_regs.c diff | blob | history
MicroBlaze GIT Repository