From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
fuqiang wang <fuqiang.wng@gmail.com>
Subject: [PATCH v6 0/4] KVM: x86: Fix hard lockup with periodic timer in guest
Date: Thu, 13 Nov 2025 12:51:10 -0800 [thread overview]
Message-ID: <20251113205114.1647493-1-seanjc@google.com> (raw)
fuqiang's patch/series to fix a bug in KVM's local APIC timer emulation where
it can trigger a hard lockup due to restarting an hrtimer with an expired
deadline over and over (and over).
v6:
- Split the apic_timer_fn() change to a separate patch (mainly for a
bisection point).
- Handle (and WARN on) period=0 in apic_timer_fn().
- Add a patch to grab a pointer to the kvm_timer struct locally.
- Tag the fixes (and prep work) for stable@.
v5:
- https://lore.kernel.org/all/20251107034802.39763-1-fuqiang.wng@gmail.com
- Add more details in commit messages and letters.
v4:
- https://lore.kernel.org/all/20251105135340.33335-1-fuqiang.wng@gmail.com
- merge two patch into one
v3:
- https://lore.kernel.org/all/20251022150055.2531-1-fuqiang.wng@gmail.com
- Fix: advanced SW timer (hrtimer) expiration does not catch up to current
time.
- optimize the commit message of patch 2
v2:
- https://lore.kernel.org/all/20251021154052.17132-1-fuqiang.wng@gmail.com
- Added a bugfix for hardlockup in v2
v1: https://lore.kernel.org/all/20251013125117.87739-1-fuqiang.wng@gmail.com
Sean Christopherson (2):
KVM: x86: WARN if hrtimer callback for periodic APIC timer fires with
period=0
KVM: x86: Grab lapic_timer in a local variable to cleanup periodic
code
fuqiang wang (2):
KVM: x86: Explicitly set new periodic hrtimer expiration in
apic_timer_fn()
KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic
HV timer
arch/x86/kvm/lapic.c | 44 +++++++++++++++++++++++++++++++-------------
1 file changed, 31 insertions(+), 13 deletions(-)
base-commit: 16ec4fb4ac95d878b879192d280db2baeec43272
--
2.52.0.rc1.455.g30608eb744-goog
next reply other threads:[~2025-11-13 20:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 20:51 Sean Christopherson [this message]
2025-11-13 20:51 ` [PATCH v6 1/4] KVM: x86: WARN if hrtimer callback for periodic APIC timer fires with period=0 Sean Christopherson
2025-11-13 20:51 ` [PATCH v6 2/4] KVM: x86: Explicitly set new periodic hrtimer expiration in apic_timer_fn() Sean Christopherson
2025-11-13 20:51 ` [PATCH v6 3/4] KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer Sean Christopherson
2025-11-13 20:51 ` [PATCH v6 4/4] KVM: x86: Grab lapic_timer in a local variable to cleanup periodic code Sean Christopherson
2025-11-18 23:27 ` [PATCH v6 0/4] KVM: x86: Fix hard lockup with periodic timer in guest 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=20251113205114.1647493-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=fuqiang.wng@gmail.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
all inboxes | Powered by JetHome®