From: Guangbo Cui <jckeep.cuiguangbo@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: Waiman Long <longman@redhat.com>,
linux-rt-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org,
Guangbo Cui <jckeep.cuiguangbo@gmail.com>
Subject: [PATCH v4 0/2] PCI/aer_inject: Adjust locking for PREEMPT_RT
Date: Sun, 2 Nov 2025 10:57:04 +0000 [thread overview]
Message-ID: <20251102105706.7259-1-jckeep.cuiguangbo@gmail.com> (raw)
This patch series addresses locking issues in the AER injection
path under PREEMPT_RT.
Signed-off-by: Guangbo Cui <jckeep.cuiguangbo@gmail.com>
---
Changes in v4:
- Reverse the patch ordering.
- Link to v2: https://lore.kernel.org/all/20251026044335.19049-2-jckeep.cuiguangbo@gmail.com/
Changes in v3:
- Remove unnecessary lock in aer_inject_exit.
- Link to v2: https://lore.kernel.org/all/20251009150651.93618-1-jckeep.cuiguangbo@gmail.com/
---
Guangbo Cui (2):
PCI/aer_inject: Remove unnecessary lock in aer_inject_exit
PCI/aer_inject: Convert inject_lock to raw_spinlock_t
drivers/pci/pcie/aer_inject.c | 33 +++++++++++++++------------------
1 file changed, 15 insertions(+), 18 deletions(-)
--
2.43.0
next reply other threads:[~2025-11-02 10:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-02 10:57 Guangbo Cui [this message]
2025-11-02 10:57 ` [PATCH v4 1/2] PCI/aer_inject: Remove unnecessary lock in aer_inject_exit Guangbo Cui
2025-11-02 10:57 ` [PATCH v4 2/2] PCI/aer_inject: Convert inject_lock to raw_spinlock_t Guangbo Cui
2025-11-03 19:21 ` Peter Zijlstra
2025-11-03 19:27 ` Peter Zijlstra
2025-11-06 13:08 ` Guangbo Cui
2025-11-06 14:05 ` Peter Zijlstra
2025-11-11 14:39 ` Sebastian Andrzej Siewior
2025-11-03 20:02 ` Sebastian Andrzej Siewior
2025-11-03 20:29 ` Peter Zijlstra
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=20251102105706.7259-1-jckeep.cuiguangbo@gmail.com \
--to=jckeep.cuiguangbo@gmail.com \
--cc=bhelgaas@google.com \
--cc=bigeasy@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=clrkwllms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=will@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 read-only IMAP folder(s) and NNTP newsgroup(s).