From: Sean Christopherson <seanjc@google.com>
To: Zenghui Yu <yuzenghui@huawei.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Sasha Levin <sashal@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Maxim Levitsky <mlevitsk@redhat.com>,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH MANUALSEL 5.10 1/2] KVM: x86: lapic: don't touch irr_pending in kvm_apic_update_apicv when inhibiting it
Date: Mon, 25 Jul 2022 23:49:21 +0000 [thread overview]
Message-ID: <Yt8sAWd6qvEtZVji@google.com> (raw)
In-Reply-To: <6d900dc3-44c0-5a0d-a545-1a51936e6a80@huawei.com>
On Mon, Jul 25, 2022, Zenghui Yu wrote:
> Hi,
>
> On 2022/3/2 1:10, Paolo Bonzini wrote:
> > On 2/22/22 15:05, Sasha Levin wrote:
> > > From: Maxim Levitsky <mlevitsk@redhat.com>
> > >
> > > [ Upstream commit 755c2bf878607dbddb1423df9abf16b82205896f ]
> >
> > Acked-by: Paolo Bonzini <pbonzini@redhat.com>
>
> What prevented it to be accepted into 5.10-stable? It can still be
> applied cleanly on top of linux-5.10.y.
KVM opts out of the AUTOSEL logic and instead uses MANUALSEL. The basic idea is
the same, use scripts/magic to determine what commits that _aren't_ tagged with an
explicit "Cc: stable@vger.kernel.org" should be backported to stable trees, the
difference being that MANUALSEL requires an explicit Acked-by from the maintainer.
Many (most?) of the automatically selected patches for KVM are good stable candidates,
but there are enough selected patches that we _don't_ want backported that the "apply
unless there's an objection" model of AUTOSEL is a bit too risky for us.
next prev parent reply other threads:[~2022-07-25 23:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 14:05 [PATCH MANUALSEL 5.10 1/2] KVM: x86: lapic: don't touch irr_pending in kvm_apic_update_apicv when inhibiting it Sasha Levin
2022-02-22 14:05 ` [PATCH MANUALSEL 5.10 2/2] KVM: x86: nSVM: deal with L1 hypervisor that intercepts interrupts but lets L2 control them Sasha Levin
2022-03-01 17:10 ` Paolo Bonzini
2022-03-01 17:10 ` [PATCH MANUALSEL 5.10 1/2] KVM: x86: lapic: don't touch irr_pending in kvm_apic_update_apicv when inhibiting it Paolo Bonzini
2022-07-25 3:29 ` Zenghui Yu
2022-07-25 23:49 ` Sean Christopherson [this message]
2022-07-26 16:29 ` Paolo Bonzini
2022-07-26 17:50 ` 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=Yt8sAWd6qvEtZVji@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yuzenghui@huawei.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.