kvm.vger.kernel.org archive mirror
 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: Misc changes for 6.6
Date: Thu, 31 Aug 2023 11:27:01 -0700	[thread overview]
Message-ID: <ZPDbdTIUXAnvL7SM@google.com> (raw)
In-Reply-To: <CABgObfay4FKV=foWLZzAWaC2kVHRnF1ib+6NC058QVZVFhGeyA@mail.gmail.com>

On Thu, Aug 31, 2023, Paolo Bonzini wrote:
> This is definitely stuff that I wish I took a look for earlier (and
> this is also why I prefer small bits over the development period, as
> it keeps me honest),

I'll work on making this happen.  I think the biggest thing on my end is to make
it easier to track/merge arbitrary topic branches, e.g. so that I can put big
series into their own branches with minimal risk of forgetting to merge them into
kvm-x86/next.

> I'll take a look but I've pulled it anyway.

FWIW, I despise the "goverened features" name, though I like the guest_can_use()
name.

> BTW, not using filemap turned out to be much bigger, and to some
> extent uglier, than I expected. I'll send a message to the private mem
> thread, but I think we should not pursue that for now and do it in a
> separate patch series (if at all) so that it's clearer what filemap_*
> code is being replaced by custom code.

Bummer, I was hoping we could avoid having to touch mm/ code.

  reply	other threads:[~2023-08-31 18:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30  0:06 [GIT PULL] KVM: x86 pull requests for 6.6 Sean Christopherson
2023-08-30  0:06 ` [GIT PULL] KVM: Non-x86 changes " Sean Christopherson
2023-08-31 17:20   ` Paolo Bonzini
2023-08-30  0:06 ` [GIT PULL] KVM: x86: Misc " Sean Christopherson
2023-08-31 17:39   ` Paolo Bonzini
2023-08-31 18:27     ` Sean Christopherson [this message]
2023-08-30  0:06 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2023-08-31 17:27   ` Sean Christopherson
2023-08-31 17:43     ` Paolo Bonzini
2023-09-01 18:43       ` Sean Christopherson
2023-09-01 21:07         ` Paolo Bonzini
2023-09-01 21:49           ` Sean Christopherson
2023-08-30  0:06 ` [GIT PULL] KVM: x86: PMU " Sean Christopherson
2023-08-31 17:31   ` Paolo Bonzini
2023-08-30  0:06 ` [GIT PULL] KVM: x86: Selftests " Sean Christopherson
2023-08-31 17:21   ` Paolo Bonzini
2023-08-30  0:06 ` [GIT PULL] KVM: x86: SVM " Sean Christopherson
2023-08-30  0:06 ` [GIT PULL] KVM: x86: VMX " Sean Christopherson
2023-08-31 17:32   ` Paolo Bonzini
2023-08-31 17:30 ` [GIT PULL] KVM: x86 pull requests " Paolo Bonzini

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=ZPDbdTIUXAnvL7SM@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;
as well as URLs for NNTP newsgroup(s).