From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Nikolay Borisov <nik.borisov@suse.com>,
x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: User mutex guards to eliminate __kvm_x86_vendor_init()
Date: Mon, 30 Oct 2023 18:45:11 +0100 [thread overview]
Message-ID: <1885f804-3601-4b3b-b8a3-534d7e8db53c@redhat.com> (raw)
In-Reply-To: <ZT_ppBmxdd6917cl@google.com>
On 10/30/23 18:36, Sean Christopherson wrote:
>>> If there are no objections, I'll massage the change log to
>>> the below when applying (for 6.8, in a few weeks).
>>
>> I think this is a "Speak Now or Forever Rest in Peace" situation. I'm going
>> to wait a couple days more for reviews to come in, post a v14 myself, and
>> apply the series to kvm/next as soon as Linus merges the 6.7 changes. The
>> series will be based on the 6.7 tags/for-linus, and when 6.7-rc1 comes up,
>> I'll do this to straighten the history:
>
> Heh, I'm pretty sure you meant to respond to the guest_memfd series.
Well, it was the "in a few weeks" that almost caused me a panic attack.
:) But yeah, I soon got to the conclusion that this required a wider
diffusion and reposted there.
Paolo
next prev parent reply other threads:[~2023-10-30 17:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 14:17 [PATCH] KVM: x86: User mutex guards to eliminate __kvm_x86_vendor_init() Nikolay Borisov
2023-10-30 16:07 ` Sean Christopherson
2023-10-30 16:17 ` Nikolay Borisov
2023-11-01 6:33 ` Huang, Kai
2023-10-30 17:10 ` Paolo Bonzini
2023-10-30 17:36 ` Sean Christopherson
2023-10-30 17:45 ` Paolo Bonzini [this message]
2023-12-09 11:57 ` Nikolay Borisov
2023-12-12 2:21 ` Sean Christopherson
2024-01-31 0:59 ` 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=1885f804-3601-4b3b-b8a3-534d7e8db53c@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nik.borisov@suse.com \
--cc=seanjc@google.com \
--cc=x86@kernel.org \
/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