All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] KVM: x86 (and a PPC) fixes for 7.0-rc3+
Date: Thu, 12 Mar 2026 08:50:27 -0700	[thread overview]
Message-ID: <abLgw1j1W4N7bsf6@google.com> (raw)
In-Reply-To: <CABgObfbnKz5HpwXMW+TjLRgQbuoiga2M-cXJ6no=K8hFsd9MCA@mail.gmail.com>

On Thu, Mar 12, 2026, Paolo Bonzini wrote:
> On Thu, Mar 12, 2026 at 3:18 PM Sean Christopherson <seanjc@google.com> wrote:
> >
> > On Wed, Mar 11, 2026, Paolo Bonzini wrote:
> > > On Tue, Mar 10, 2026 at 10:20 PM Sean Christopherson <seanjc@google.com> wrote:
> > > >
> > > > On Thu, Mar 05, 2026, Sean Christopherson wrote:
> > > > >  - Update CR8 write interception when AVIC is (de)activated to fix a bug where
> > > > >    KVM can run with the CR8 intercept in perpetuity.
> > > >
> > > > ...
> > > >
> > > > > Sean Christopherson (4):
> > > > >       KVM: SVM: Initialize AVIC VMCB fields if AVIC is enabled with in-kernel APIC
> > > > >       KVM: SVM: Set/clear CR8 write interception when AVIC is (de)activated
> > > >
> > > > The CR8 write patch broke SEV-ES guests.  If you haven't already prepared the
> > > > PULL request for Linus, can you apply the fix directly?
> > >
> > > Done.
> >
> > No?  I see the pull request in kvm.git, but not the below fix-to-the-fix.
> 
> Ah, I had squashed it in directly from the original thread.

OMG, -ENOCOFFEE x2.  I even looked at commit 87d0f901a9bd from your tree, and
the lack of a merge commit for fixes should have been a big clue.

> I have now added on top the testcase.

Thanks much!

      reply	other threads:[~2026-03-12 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05 19:30 [GIT PULL] KVM: x86 (and a PPC) fixes for 7.0-rc3+ Sean Christopherson
2026-03-10 21:20 ` Sean Christopherson
2026-03-11 18:05   ` Paolo Bonzini
2026-03-12 14:18     ` Sean Christopherson
2026-03-12 15:44       ` Paolo Bonzini
2026-03-12 15:50         ` Sean Christopherson [this message]

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=abLgw1j1W4N7bsf6@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.