From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "peterz@infradead.org" <peterz@infradead.org>,
"tglx@kernel.org" <tglx@kernel.org>
Cc: "Wu, Binbin" <binbin.wu@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"bonzini@redhat.com" <bonzini@redhat.com>,
"seanjc@google.com" <seanjc@google.com>,
"binbin.wu@linux.intel.com" <binbin.wu@linux.intel.com>,
"Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: CPU Lockups in KVM with deferred hrtimer rearming
Date: Tue, 21 Apr 2026 19:18:21 +0000 [thread overview]
Message-ID: <819b1ab82054ee4f08a64961b13e4fb433eaa62e.camel@intel.com> (raw)
In-Reply-To: <87cxzsb5n0.ffs@tglx>
On Tue, 2026-04-21 at 19:11 +0200, Thomas Gleixner wrote:
>
> Now for VMX, that hrtimer_rearm_deferred() call should really go into
> handle_external_interrupt_irqoff(), which in turn requires to export
> __hrtimer_rearm_deferred().
>
> But we can avoid that alltogether. Something like the untested below.
Tested with the below patch and the tests pass with this too.
>
> Thanks,
>
> tglx
> ---
> --- a/kernel/time/hrtimer.c
> +++ b/kernel/time/hrtimer.c
> @@ -42,9 +42,10 @@
> #include <linux/timer.h>
> #include <linux/freezer.h>
> #include <linux/compat.h>
> -
> #include <linux/uaccess.h>
>
> +#include <asm/irq_regs.h>
> +
> #include <trace/events/timer.h>
>
> #include "tick-internal.h"
> @@ -2062,11 +2063,16 @@ void __hrtimer_rearm_deferred(void)
> static __always_inline void
> hrtimer_interrupt_rearm(struct hrtimer_cpu_base *cpu_base, ktime_t expires_next)
> {
> - /* hrtimer_interrupt() just re-evaluated the first expiring timer */
> - cpu_base->deferred_needs_update = false;
> - /* Cache the expiry time */
> - cpu_base->deferred_expires_next = expires_next;
> - set_thread_flag(TIF_HRTIMER_REARM);
> + /* Lies, damned lies and virt */
> + if (likely(!regs_irqs_disabled(get_irq_regs()))) {
> + /* hrtimer_interrupt() just re-evaluated the first expiring timer */
> + cpu_base->deferred_needs_update = false;
> + /* Cache the expiry time */
> + cpu_base->deferred_expires_next = expires_next;
> + set_thread_flag(TIF_HRTIMER_REARM);
> + } else {
> + hrtimer_rearm(cpu_base, expires_next, false);
> + }
> }
> #else /* CONFIG_HRTIMER_REARM_DEFERRED */
> static __always_inline void
>
next prev parent reply other threads:[~2026-04-21 19:18 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 20:50 CPU Lockups in KVM with deferred hrtimer rearming Verma, Vishal L
2026-04-20 15:00 ` Thomas Gleixner
2026-04-20 15:22 ` Thomas Gleixner
2026-04-20 20:57 ` Verma, Vishal L
2026-04-20 22:19 ` Thomas Gleixner
2026-04-20 22:24 ` Verma, Vishal L
2026-04-21 6:29 ` Thomas Gleixner
2026-04-21 4:51 ` Binbin Wu
2026-04-21 7:39 ` Thomas Gleixner
2026-04-21 11:18 ` Peter Zijlstra
2026-04-21 11:32 ` Peter Zijlstra
2026-04-21 11:34 ` Peter Zijlstra
2026-04-21 11:49 ` Peter Zijlstra
2026-04-21 12:05 ` Peter Zijlstra
2026-04-21 13:19 ` Peter Zijlstra
2026-04-21 13:29 ` Peter Zijlstra
2026-04-21 16:36 ` Thomas Gleixner
2026-04-21 18:11 ` Verma, Vishal L
2026-04-21 17:11 ` Thomas Gleixner
2026-04-21 17:20 ` Jim Mattson
2026-04-21 18:29 ` Thomas Gleixner
2026-04-21 18:55 ` Sean Christopherson
2026-04-21 20:06 ` Peter Zijlstra
2026-04-21 20:46 ` Peter Zijlstra
2026-04-21 20:57 ` Sean Christopherson
2026-04-21 21:02 ` Peter Zijlstra
2026-04-21 21:42 ` Sean Christopherson
2026-04-21 20:39 ` Paolo Bonzini
2026-04-21 21:02 ` Sean Christopherson
2026-04-21 21:49 ` Thomas Gleixner
2026-04-21 22:07 ` Sean Christopherson
2026-04-21 22:24 ` Paolo Bonzini
2026-04-21 19:18 ` Verma, Vishal L [this message]
2026-04-21 16:30 ` Thomas Gleixner
2026-04-21 16:11 ` Verma, Vishal L
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=819b1ab82054ee4f08a64961b13e4fb433eaa62e.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=binbin.wu@intel.com \
--cc=binbin.wu@linux.intel.com \
--cc=bonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=tglx@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