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: SVM changes for 6.19
Date: Wed, 26 Nov 2025 05:41:48 -0800 [thread overview]
Message-ID: <aScDnAYCtGYXG2S1@google.com> (raw)
In-Reply-To: <CABgObfbU8kXE3xKzYg3HETFw+FURXj3MjXmDnhoL=qA+OLO-CQ@mail.gmail.com>
On Wed, Nov 26, 2025, Paolo Bonzini wrote:
> On Wed, Nov 26, 2025 at 2:45 AM Sean Christopherson <seanjc@google.com> wrote:
> >
> > A handful of lowish priority nSVM fixes, AVIC support for 4k vCPUs, and new
> > uAPI to advertise SNP policy bits to userspace.
> >
> > Side topic, this pull request is finally proof that I don't just merge my own
> > stuff :-D
>
> What do you mean? Is there anything you want me to review?
Oh, it was purely a joke. I don't have any commits in this particular pull request,
and that caught my eye when looking at the shortlog.
next prev parent reply other threads:[~2025-11-26 13:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 1:44 [GIT PULL] KVM: x86 pull requests 6.19 Sean Christopherson
2025-11-26 1:44 ` [GIT PULL] KVM: Generic changes for 6.19 Sean Christopherson
2025-11-26 8:59 ` Paolo Bonzini
2025-11-26 1:44 ` [GIT PULL] KVM: guest_memfd: NUMA support and other " Sean Christopherson
2025-11-26 8:33 ` Paolo Bonzini
2025-11-26 1:44 ` [GIT PULL] KVM: x86: Misc " Sean Christopherson
2025-11-26 8:49 ` Paolo Bonzini
2025-11-26 1:44 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2025-11-26 8:50 ` Paolo Bonzini
2025-11-26 1:44 ` [GIT PULL] KVM: x86: Selftests " Sean Christopherson
2025-11-26 8:51 ` Paolo Bonzini
2025-11-26 1:44 ` [GIT PULL] KVM: x86: SVM " Sean Christopherson
2025-11-26 8:48 ` Paolo Bonzini
2025-11-26 13:41 ` Sean Christopherson [this message]
2025-11-26 1:44 ` [GIT PULL] KVM: x86: TDX " Sean Christopherson
2025-11-26 8:51 ` Paolo Bonzini
2025-11-26 1:44 ` [GIT PULL] KVM: x86: VMX " Sean Christopherson
2025-11-26 8:50 ` Paolo Bonzini
2025-11-26 13:42 ` Sean Christopherson
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=aScDnAYCtGYXG2S1@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.