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: Mon, 26 Sep 2022 16:23:08 +0000	[thread overview]
Message-ID: <YzHR7I2CIzT9itFp@google.com> (raw)
In-Reply-To: <CABgObfY5VRxSfKX_EoubCdaimDAhvdnZ8NhgZZXRVnQFmboi8Q@mail.gmail.com>

On Mon, Sep 26, 2022, Paolo Bonzini wrote:
> On Wed, Sep 21, 2022 at 1:17 AM Sean Christopherson <seanjc@google.com> 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.
> >
> > Note, there's one arm64 patch hiding in here to account KVM's stage-2 page
> > tables in the kernel's memory stats.
> 
> Thanks, I didn't get a respin so I just rebased to remove the problematic
> commits.

Sorry, was planning on getting that done today.

> >   - The aforementioned nested events series (Paolo, Sean)
> 
> Applied on top.
> 
> >   - APICv/AVIC fixes/cleanups (Sean)
> >   - Hyper-V TLB flush enhancements (Vitaly)
> 
> These should wait for 6.2.

Agreed, I was overly optimistic in hoping the series wouldn't require additional
changes.

> >   - Small-ish PMU fixes (Like, Sean)
> >   - Misc cleanups (Miaohe, et al)
> 
> These can be in a separate pull request.

I think it makes sense to grab a few "safe" PMU fixes from Like, but for everything
else I'll wait for 6.2 as well.

Thanks!

      reply	other threads:[~2022-09-26 17:13 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
2022-09-26 16:09 ` Paolo Bonzini
2022-09-26 16:23   ` 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=YzHR7I2CIzT9itFp@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.