From: Thomas Gleixner <tglx@linutronix.de>
To: Lukas Wunner <lukas@wunner.de>, Zijiang Huang <huangzjsmile@gmail.com>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org,
Zijiang Huang <kerayhuang@tencent.com>,
Hao Peng <flyingpeng@tencent.com>
Subject: Re: [PATCH] PCI: Using lockless config space accessors based on Kconfig option
Date: Wed, 07 May 2025 11:11:23 +0200 [thread overview]
Message-ID: <87jz6sn5tw.ffs@tglx> (raw)
In-Reply-To: <aBsRXO6Us_wsdhji@wunner.de>
On Wed, May 07 2025 at 09:53, Lukas Wunner wrote:
> On Wed, May 07, 2025 at 03:30:28PM +0800, Zijiang Huang wrote:
> The question is, why did the commit only replace raw_spin_lock()
> with pci_lock_config() in the in-kernel PCI accessors, but not in
> the user space accessors? Is it safe to replace it there as well?
See comment above pci_cfg_access_lock() ...
prev parent reply other threads:[~2025-05-07 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 7:30 [PATCH] PCI: Using lockless config space accessors based on Kconfig option Zijiang Huang
2025-05-07 7:53 ` Lukas Wunner
2025-05-07 9:04 ` [PATCH] PCI: Using lockless config space accessors based on Zijiang Huang
2025-05-07 14:00 ` Thomas Gleixner
2025-05-07 9:11 ` Thomas Gleixner [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=87jz6sn5tw.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bhelgaas@google.com \
--cc=flyingpeng@tencent.com \
--cc=huangzjsmile@gmail.com \
--cc=kerayhuang@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
/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