public inbox for kvm@vger.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 pull requests 6.18
Date: Tue, 30 Sep 2025 12:16:48 -0700	[thread overview]
Message-ID: <aNwsoK82jW97xy9Y@google.com> (raw)
In-Reply-To: <CABgObfY6iEKbo9tLAGdsKhK3vYsFW3MB_6X4ay8GAmQv-oRBGQ@mail.gmail.com>

On Tue, Sep 30, 2025, Paolo Bonzini wrote:
> On Sat, Sep 27, 2025 at 8:09 AM Sean Christopherson <seanjc@google.com> wrote:
> >
> > Sorry this is coming in late, it's been a long week.
> >
> > Similar to 6.17, a few anomolies in the form of external and cross-branch
> > dependencies, but thankfully only one conflict that I know of (details in
> > CET pull request).  Oh, and one "big" anomoly: there's a pull request for
> > guest-side x86/kvm changes (but it's small, hence the quotes).
> >
> > I tried my best to document anything unusual in the individual pull requests,
> > so hopefully nothing is too surprising.
> 
> Quite big with CET and the FRED preparations, but no surprises indeed.
> 
> Because of the conflict, I'll delay the bulk of these to a separate
> pull request, probably on Friday.
> 
> I have already included (and tested on top of 6.17) the selftests,
> guest and generic pull request. Everything else in kvm/next. As I
> mentioned in the reply to the individual PR, I ended up cherry-picking
> the module patches.

Roger that.  I updated kvm-x86/next to kvm/next, so we shouldn't get yelled at
for having duplicate commits.

> There were a couple preparatory patches that I guess could have been in misc,

Oh, yeah, that's super obvious in hindsight.

Thanks!

      reply	other threads:[~2025-09-30 19:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-27  6:09 [GIT PULL] KVM: x86 pull requests 6.18 Sean Christopherson
2025-09-27  6:09 ` [GIT PULL] x86/kvm: Guest side changes for 6.18 Sean Christopherson
2025-09-30 17:28   ` Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: One lone common change " Sean Christopherson
2025-09-30 17:28   ` Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: x86: MMU changes " Sean Christopherson
2025-09-30 17:33   ` Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: Selftests " Sean Christopherson
2025-09-30 17:24   ` Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: x86: VMX " Sean Christopherson
2025-09-30 17:33   ` Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: x86: SVM " Sean Christopherson
2025-09-30 17:35   ` Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: x86: SNP CipherTextHiding " Sean Christopherson
2025-09-30 17:35   ` Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: x86: Misc changes " Sean Christopherson
2025-09-30 18:06   ` Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: x86: CET virtualization " Sean Christopherson
2025-09-27  6:09 ` [GIT PULL] KVM: Symbol export restrictions " Sean Christopherson
2025-09-30 17:41   ` Paolo Bonzini
2025-09-30 18:10 ` [GIT PULL] KVM: x86 pull requests 6.18 Paolo Bonzini
2025-09-30 19:16   ` 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=aNwsoK82jW97xy9Y@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox