From: Sean Christopherson <seanjc@google.com>
To: Haitao Shan <hshan@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] KVM: x86: Fix lapic timer interrupt lost after loading a snapshot.
Date: Fri, 29 Sep 2023 10:11:35 -0700 [thread overview]
Message-ID: <ZRcFR6Tf-9QzfbnD@google.com> (raw)
In-Reply-To: <CAGD3tSxPDVb9sN1g+gTV5SykY57Szpx1SjEcmHJvK62u1fiXmA@mail.gmail.com>
On Fri, Sep 29, 2023, Haitao Shan wrote:
> Thank you very much.
>
> I do have one more question. Is this fix going to be backported to
> v6.3, v6.4, etc? Or perhaps that will be a decision made by other
> maintainers? The reason for such a question is to decide whether we
> have to keep the workaround for certain kernel versions.
It's tagged for stable, so it'll get automatically selected/backported for stable
kernels so long as the patch applies cleanly. That won't include 6.3 or 6.4
because those are already end-of-life, i.e. not LTS kernels, and not the most
recent release.
If the patch doesn't apply cleanly, e.g. I highly doubt it'll apply as-is for 5.15,
then someone has to do a manual backport, where "someone" can be anyone. Sometimes
that's a maintainer, but just as often it's someone that really cares about fixing
something in a particular kernel.
next prev parent reply other threads:[~2023-09-29 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 23:55 [PATCH v3] KVM: x86: Fix lapic timer interrupt lost after loading a snapshot Haitao Shan
2023-09-29 2:20 ` Sean Christopherson
2023-09-29 16:31 ` Haitao Shan
2023-09-29 17:11 ` Sean Christopherson [this message]
2023-09-29 23:51 ` Haitao Shan
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=ZRcFR6Tf-9QzfbnD@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=hshan@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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