mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] KVM: x86: Changes for 6.17
Date: Mon, 28 Jul 2025 17:50:42 +0200	[thread overview]
Message-ID: <CABgObfYFfOuoh5fcZCfuuZtJ2LqZe+GOASjj8O2O-vUa08pA5g@mail.gmail.com> (raw)
In-Reply-To: <20250725220713.264711-1-seanjc@google.com>

On Sat, Jul 26, 2025 at 12:07 AM Sean Christopherson <seanjc@google.com> wrote:
>
> As promised, the storm has arrived :-)
>
> There are a two anomalies this time around, but thankfully only one conflict,
> and a trivial one at that (details on that in the MMIO Stale Data pull request).
>
> 1. The "no assignment" pull request depends on the IRQs and MMIO Stale Data
>    pull requests.  I created the topic branch based on the IRQs branch (minus
>    one commit that came in later), and then merged in the MMIO branch to create
>    a common base.  All the commits came out as I wanted, but the diff stats
>    generated by `git request-pull` are funky, so I doctored them up, a lot.
>
> 2. The "SEV cache maintenance" pull request is based on a tag/branch from the
>    tip tree.  I don't think you need to do anything special here?  Except
>    possibly mention it to Linus if the KVM pull request happens to get sent
>    before the associated tip pull request (which seems unlikely given how they
>    send a bunch of small pulls).

Pulled everything except the lone TDX commit, thanks. I'm going to
start testing without it.

Paolo


      parent reply	other threads:[~2025-07-28 15:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-25 22:07 Sean Christopherson
2025-07-25 22:07 ` [GIT PULL] KVM: x86: Local APIC refactoring " Sean Christopherson
2025-07-25 22:07 ` [GIT PULL] KVM: Dirty Ring changes " Sean Christopherson
2025-07-25 22:07 ` [GIT PULL] KVM: Generic " Sean Christopherson
2025-07-25 22:07 ` [GIT PULL] KVM: IRQ " Sean Christopherson
2025-07-25 22:07 ` [GIT PULL] KVM: x86: Misc " Sean Christopherson
2025-07-28 15:11   ` Paolo Bonzini
2025-07-25 22:07 ` [GIT PULL] KVM: x86: MMIO State Data mitigation " Sean Christopherson
2025-07-25 22:07 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2025-07-25 22:07 ` [GIT PULL] KVM: Device assignment accounting " Sean Christopherson
2025-07-28 15:08   ` Paolo Bonzini
2025-07-25 22:07 ` [GIT PULL] KVM: x86: Selftests " Sean Christopherson
2025-07-25 22:07 ` [GIT PULL] KVM: x86: SEV " Sean Christopherson
2025-07-25 22:07 ` [GIT PULL] KVM: x86: SVM " Sean Christopherson
2025-07-25 22:07 ` [GIT PULL] KVM: x86: VMX " Sean Christopherson
2025-07-28 15:47   ` Paolo Bonzini
2025-07-29 19:44     ` Sean Christopherson
2025-07-30 17:55       ` Paolo Bonzini
2025-07-28 15:50 ` Paolo Bonzini [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=CABgObfYFfOuoh5fcZCfuuZtJ2LqZe+GOASjj8O2O-vUa08pA5g@mail.gmail.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seanjc@google.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

all inboxes | Powered by JetHome®