From: "Krzysztof Wilczyński" <kw@linux.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-pci@vger.kernel.org,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
Ryo Takakura <ryotkkr98@gmail.com>,
bhelgaas@google.com, jonathan.derrick@linux.dev,
lpieralisi@kernel.org, manivannan.sadhasivam@linaro.org,
nirmal.patel@linux.intel.com, robh@kernel.org,
rostedt@goodmis.org, kbusch@kernel.org,
linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH v4] PCI: vmd: Make vmd_dev::cfg_lock a raw_spinlock_t.
Date: Thu, 20 Feb 2025 23:51:27 +0900 [thread overview]
Message-ID: <20250220145127.GC1777078@rocinante> (raw)
In-Reply-To: <20250218080830.ufw3IgyX@linutronix.de>
Hello,
> The access to the PCI config space via pci_ops::read and pci_ops::write
> is a low-level hardware access. The functions can be accessed with
> disabled interrupts even on PREEMPT_RT. The pci_lock has been made a
> raw_spinlock_t for this purpose. A spinlock_t becomes a sleeping lock on
> PREEMPT_RT can not be acquired with disabled interrupts.
> The vmd_dev::cfg_lock is accessed in the same context as the pci_lock.
>
> Make vmd_dev::cfg_lock a raw_spinlock_t.
Applied to controller/vmd, thank you!
Krzysztof
next prev parent reply other threads:[~2025-02-20 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 8:08 [PATCH v4] PCI: vmd: Make vmd_dev::cfg_lock a raw_spinlock_t Sebastian Andrzej Siewior
2025-02-20 14:51 ` Krzysztof Wilczyński [this message]
2025-02-20 22:59 ` Bjorn Helgaas
2025-02-21 1:17 ` Krzysztof Wilczyński
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=20250220145127.GC1777078@rocinante \
--to=kw@linux.com \
--cc=bhelgaas@google.com \
--cc=bigeasy@linutronix.de \
--cc=jonathan.derrick@linux.dev \
--cc=kbusch@kernel.org \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=nirmal.patel@linux.intel.com \
--cc=robh@kernel.org \
--cc=rostedt@goodmis.org \
--cc=ryotkkr98@gmail.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