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
Subject: Re: [GIT PULL] KVM: x86: First batch of updates for 6.1, i.e. kvm/queue
Date: Thu, 22 Sep 2022 19:41:42 +0000	[thread overview]
Message-ID: <Yyy6dv+07D3OR1K+@google.com> (raw)
In-Reply-To: <Yysjz3e8y4ij0l0a@google.com>

On Wed, Sep 21, 2022, Sean Christopherson wrote:
> On Tue, Sep 20, 2022, Sean Christopherson wrote:
> > First batch of x86 updates for 6.1, i.e. for kvm/queue.  I was planning to get
> > this out (much) earlier and in a smaller batch, but KVM Forum and the INIT bug
> > I initially missed in the nested events series threw a wrench in those plans.
> 
> ...
> 
> >  - Precisely track NX huge page accounting.
> 
> Abort!  Abort!  Abort!
> 
> Please don't pull, the NX series is embarrasingly broken[*].  It could probably
> be fixed up, but I'd much rather redo the series for 6.2.
> 
> [*] https://lore.kernel.org/all/87tu50oohn.fsf@redhat.com

...

> Jinpeng Cui (1):
>       KVM: x86/mmu: remove superfluous local variable "r"

> ye xingchen (1):
>       KVM: x86: Remove the unneeded "ret" in kvm_vm_ioctl_set_tss_addr()


I'm also going to drop two these cleanups, Shuah pointed out[1] that patches from
this common gmail account shouldn't be accepted in their current form[2].

[1] https://lore.kernel.org/all/b9044b55-1498-3309-4db5-70ca2c20b3f7@linuxfoundation.org
[2] https://lore.kernel.org/all/Yylv5hbSBejJ58nt@kroah.com

  reply	other threads:[~2022-09-22 19:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 23:16 [GIT PULL] KVM: x86: First batch of updates for 6.1, i.e. kvm/queue Sean Christopherson
2022-09-21 14:46 ` Sean Christopherson
2022-09-22 19:41   ` Sean Christopherson [this message]
2022-09-26 16:09 ` Paolo Bonzini
2022-09-26 16:23   ` 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=Yyy6dv+07D3OR1K+@google.com \
    --to=seanjc@google.com \
    --cc=kvm@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.