From: Sean Christopherson <seanjc@google.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: David Woodhouse <dwmw@amazon.co.uk>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"shaikhkamal2012@gmail.com" <shaikhkamal2012@gmail.com>,
"syzbot+919877893c9d28162dc2@syzkaller.appspotmail.com"
<syzbot+919877893c9d28162dc2@syzkaller.appspotmail.com>,
"me@brighamcampbell.com" <me@brighamcampbell.com>,
"linux-rt-devel@lists.linux.dev"
<linux-rt-devel@lists.linux.dev>, "hpa@zytor.com" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"paul@xen.org" <paul@xen.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"skhan@linuxfoundation.org" <skhan@linuxfoundation.org>
Subject: Re: [PATCH] KVM: x86/xen: Fix sleeping lock in hard IRQ context on PREEMPT_RT
Date: Thu, 2 Apr 2026 15:23:13 -0700 [thread overview]
Message-ID: <ac7sUQZ0AQIMFDnL@google.com> (raw)
In-Reply-To: <20260402064209.8ba7wrBI@linutronix.de>
On Thu, Apr 02, 2026, Sebastian Andrzej Siewior wrote:
> On 2026-04-01 08:40:07 [-0700], Sean Christopherson wrote:
> > Re-reading through the thread where you proposed using trylock, and through
> > commit bbe17c625d68 ("KVM: x86/xen: Fix potential deadlock in kvm_xen_update_runstate_guest()"),
> > I think I agree with using trylock for "fast" paths.
>
> Has bbe17c625d68 been applied for PREEMPT_RT reasons?
Ya, I think it was to suppress a PREEMPT_RT-only splat:
https://lore.kernel.org/all/20240227115648.3104-8-dwmw2@infradead.org
prev parent reply other threads:[~2026-04-02 22:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 13:15 [PATCH] KVM: x86/xen: Fix sleeping lock in hard IRQ context on PREEMPT_RT shaikh.kamal
2026-03-30 14:18 ` Steven Rostedt
2026-03-30 14:51 ` Woodhouse, David
2026-04-01 15:40 ` Sean Christopherson
2026-04-02 1:30 ` [PATCH v2 0/1] KVM: x86/xen: Fix PREEMPT_RT sleeping lock bug shaikh.kamal
2026-04-02 1:31 ` [PATCH v2 1/1] KVM: x86/xen: Use trylock for fast path event channel delivery shaikh.kamal
2026-04-02 6:36 ` Sebastian Andrzej Siewior
2026-04-02 22:40 ` Sean Christopherson
2026-04-02 6:42 ` [PATCH] KVM: x86/xen: Fix sleeping lock in hard IRQ context on PREEMPT_RT Sebastian Andrzej Siewior
2026-04-02 22:23 ` Sean Christopherson [this message]
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=ac7sUQZ0AQIMFDnL@google.com \
--to=seanjc@google.com \
--cc=bigeasy@linutronix.de \
--cc=dwmw@amazon.co.uk \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=me@brighamcampbell.com \
--cc=paul@xen.org \
--cc=rostedt@goodmis.org \
--cc=shaikhkamal2012@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+919877893c9d28162dc2@syzkaller.appspotmail.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