Skip to content

KVM: SVM: Set pCPU during IRTE update if vCPU is running

Sean Christopherson kvm lkml 1 version Applied

Status from this message: Applied to kvm-x86 svm, with a massaged changelog in patch 2 to state that the

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 4 repliesApplied

Patches in v1 Applied

#Subject and filesSizeRepliesApplied
1/2KVM: SVM: Take and hold ir_list_lock when updating vCPU's Physical ID entryarch/x86/kvm/svm/avic.c+23 -80 replies
2/2KVM: SVM: Set target pCPU during IRTE update if target vCPU is runningarch/x86/kvm/svm/avic.c+28 -00 replies

Reviews trailers per patch

None of the 2 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.

PatchJoao MartinsAlejandro Jimenez
SeriesR-b T-b
1/2
2/2

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH 0/2] KVM: SVM: Set pCPU during IRTE update if vCPU is running

Fix a bug where KVM doesn't set the pCPU affinity for running vCPUs when updating IRTE routing. Not setting the pCPU means the IOMMU will signal the wrong pCPU's doorbell until the vCPU goes through a put+load cycle.

I waffled for far too long between making this one patch or two. Moving the lock doesn't make all that much sense as a standalone patch, but in the end, I decided that isolating the locking change would be useful in the unlikely event that it breaks something. If anyone feels strongly about making this a single patch, I have no objection to squashing these together.

Sean Christopherson (2):
KVM: SVM: Take and hold ir_list_lock when updating vCPU's Physical ID
entry
KVM: SVM: Set target pCPU during IRTE update if target vCPU is running

 arch/x86/kvm/svm/avic.c | 59 +++++++++++++++++++++++++++++++++++------
 1 file changed, 51 insertions(+), 8 deletions(-)

base-commit: 240f736891887939571854bd6d734b6c9291f22e

Signature · 1 line
2.41.0.640.ga95def55d0-goog