public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Naveen N Rao <naveen@kernel.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Maxim Levitsky <mlevitsk@redhat.com>,
	Vasant Hegde <vasant.hegde@amd.com>,
	 Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: [RFC PATCH 2/3] KVM: SVM: Fix IRQ window inhibit handling across multiple vCPUs
Date: Fri, 23 Jan 2026 11:55:36 -0800	[thread overview]
Message-ID: <aXPSOMClTeRKG0_V@google.com> (raw)
In-Reply-To: <aXI1EAolDjVbp_9W@blrnaveerao1>

On Thu, Jan 22, 2026, Naveen N Rao wrote:
> On Wed, Jan 14, 2026 at 11:55:57AM -0800, Sean Christopherson wrote:
> > I also want to land the optimization separately, so that it can be properly
> > documented, justified, and analyzed by others.
> > 
> > I pushed a rebased version (compile-tested only at this time) with the above change to:
> > 
> >   https://github.com/sean-jc/linux.git svm/avic_irq_window
> > 
> > Can you run you perf tests to see if that aproach also eliminates the degredation
> > relative to avic=0 that you observed?
> 
> Yes, this definitely seems to be helping get rid of that odd performance 
> drop I was seeing earlier. I'll run a couple more tests and report back 
> by next week if I see anything off. Otherwise, this is looking good to 
> me and if you want to apply this to -next, I'm fine with that:
> Tested-by: Naveen N Rao (AMD) <naveen@kernel.org>

Nice, thanks for testing!  I'll post a proper series later today (or early next
week), and will wait until after the merge window to apply (a little too close
for comfort at this point).

  reply	other threads:[~2026-01-23 19:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18  6:43 [RFC PATCH 0/3] KVM: SVM: Fix IRQ window inhibit handling Naveen N Rao (AMD)
2025-07-18  6:43 ` [RFC PATCH 1/3] KVM: SVM: Fix clearing IRQ window inhibit with nested guests Naveen N Rao (AMD)
2025-07-18  6:43 ` [RFC PATCH 2/3] KVM: SVM: Fix IRQ window inhibit handling across multiple vCPUs Naveen N Rao (AMD)
2026-01-14 19:55   ` Sean Christopherson
2026-01-14 20:19     ` Sean Christopherson
2026-01-22 14:49     ` Naveen N Rao
2026-01-23 19:55       ` Sean Christopherson [this message]
2025-07-18  6:43 ` [RFC PATCH 3/3] KVM: SVM: Optimize IRQ window inhibit handling Naveen N Rao (AMD)
2025-09-09 14:30 ` [RFC PATCH 0/3] KVM: SVM: Fix " Naveen N Rao
2025-09-09 15:34   ` Sean Christopherson
2025-09-10 12:30     ` Naveen N Rao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aXPSOMClTeRKG0_V@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlevitsk@redhat.com \
    --cc=naveen@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=vasant.hegde@amd.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox