From: David Hunter <david.hunter.linux@gmail.com>
To: seanjc@google.com
Cc: dave.hansen@linux.intel.com, david.hunter.linux@gmail.com,
hpa@zytor.com, javier.carrasco.cruz@gmail.com,
jmattson@google.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, lirongqing@baidu.com,
pbonzini@redhat.com, pshier@google.com, shuah@kernel.org,
stable@vger.kernel.org, x86@kernel.org
Subject: [PATCH 6.1.y 0/2 V2] KVM: x86: fire timer when it is migrated
Date: Mon, 26 Aug 2024 18:13:34 -0400 [thread overview]
Message-ID: <20240826221336.14023-1-david.hunter.linux@gmail.com> (raw)
In-Reply-To: <ZsSiQkQVSz0DarYC@google.com>
Hello,
I'm sending you two this first because this will be my first time
sending a series patch. Is this okay?
Backport for 6.1.y. These two commits should be backported together to
fix an issue that arrises from commit 967235d320329e4a7a2bd1a36b04293063e985ae
-Subject: 'VM: vmx: clear pending interrupts on KVM_SET_LAPIC'
[ Upstream Commit 8e6ed96cdd5001c55fccc80a17f651741c1ca7d2 ]
Haitao Shan (1):
KVM: x86: Fix lapic timer interrupt lost after loading a snapshot.
[ Upstream Commit 9cfec6d097c607e36199cf0cfbb8cf5acbd8e9b2 ]
Li RongQing (1):
KVM: x86: fire timer when it is migrated and expired, and in oneshot
mode
---
V1 --> V2
- changed to a series patch to fix an issue with the patch
arch/x86/kvm/lapic.c | 8 ++++++--
arch/x86/kvm/vmx/vmx.c | 1 +
2 files changed, 7 insertions(+), 2 deletions(-)
--
2.43.0
next prev parent reply other threads:[~2024-08-26 22:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 5:32 [PATCH 6.1.y] KVM: x86: fire timer when it is migrated and expired, and in oneshot mode David Hunter
2024-08-20 6:18 ` 答复: [外部邮件] " Li,Rongqing
2024-08-20 14:07 ` Sean Christopherson
2024-08-26 22:13 ` David Hunter [this message]
2024-08-26 22:13 ` [PATCH 6.1.y 1/2 V2] " David Hunter
2024-08-26 22:13 ` [PATCH 6.1.y 2/2 V2] KVM: x86: Fix lapic timer interrupt lost after loading a snapshot David Hunter
2024-08-27 13:10 ` Greg KH
2024-08-27 18:52 ` 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=20240826221336.14023-1-david.hunter.linux@gmail.com \
--to=david.hunter.linux@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=pbonzini@redhat.com \
--cc=pshier@google.com \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).