From: Ryo Takakura <ryotkkr98@gmail.com>
To: kbusch@kernel.org
Cc: bhelgaas@google.com, bigeasy@linutronix.de,
jonathan.derrick@linux.dev, kw@linux.com, lgoncalv@redhat.com,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-rt-devel@lists.linux.dev, lpieralisi@kernel.org,
manivannan.sadhasivam@linaro.org, nirmal.patel@linux.intel.com,
robh@kernel.org, rostedt@goodmis.org
Subject: Re: [PATCH v2] PCI: vmd: Fix spinlock usage on config access for RT kernel
Date: Thu, 19 Dec 2024 09:55:38 +0900 [thread overview]
Message-ID: <20241219005538.9125-1-ryotkkr98@gmail.com> (raw)
In-Reply-To: <Z2LsFoXotl_SHmNk@kbusch-mbp.dhcp.thefacebook.com>
Hi Keith,
On Wed, 18 Dec 2024 08:36:54 -0700, Keith Busch wrote:
>> @@ -385,13 +384,11 @@ static int vmd_pci_read(struct pci_bus *bus, unsigned int devfn, int reg,
>> {
>> struct vmd_dev *vmd = vmd_from_bus(bus);
>> void __iomem *addr = vmd_cfg_addr(vmd, bus, devfn, reg, len);
>> - unsigned long flags;
>> int ret = 0;
>>
>> if (!addr)
>> return -EFAULT;
>>
>> - spin_lock_irqsave(&vmd->cfg_lock, flags);
>> switch (len) {
>> case 1:
>> *value = readb(addr);
>
>There's a comment above this function explaining the need for the lock,
>which doesn't make a lot of sense after this patch.
Thanks for pointing it out! It slipped my mind.
I'll leave it as it is for the next patch :)
Sincerely,
Ryo Takakura
prev parent reply other threads:[~2024-12-19 0:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 11:59 [PATCH v2] PCI: vmd: Fix spinlock usage on config access for RT kernel Ryo Takakura
2024-12-18 13:17 ` Luis Claudio R. Goncalves
2024-12-18 15:36 ` Keith Busch
2024-12-18 15:48 ` Sebastian Andrzej Siewior
2024-12-18 15:57 ` Keith Busch
2024-12-18 16:03 ` Sebastian Andrzej Siewior
2024-12-18 16:35 ` Luis Claudio R. Goncalves
2024-12-19 0:53 ` Ryo Takakura
2024-12-19 0:55 ` Ryo Takakura [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=20241219005538.9125-1-ryotkkr98@gmail.com \
--to=ryotkkr98@gmail.com \
--cc=bhelgaas@google.com \
--cc=bigeasy@linutronix.de \
--cc=jonathan.derrick@linux.dev \
--cc=kbusch@kernel.org \
--cc=kw@linux.com \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.