public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: "Krzysztof Wilczyński" <kw@linux.com>
Cc: "Keith Busch" <kbusch@kernel.org>,
	"Matthew Wood" <thepacketgeek@gmail.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Mario Limonciello" <superm1@kernel.org>,
	"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [RESEND PATCH v7 1/1] PCI/sysfs: Expose PCIe device serial number
Date: Mon, 15 Sep 2025 11:03:20 +0100	[thread overview]
Message-ID: <20250915110320.0000602f@huawei.com> (raw)
In-Reply-To: <20250913061720.GA1992308@rocinante>

On Sat, 13 Sep 2025 15:17:20 +0900
Krzysztof Wilczyński <kw@linux.com> wrote:

> Hello,
> 
> > Can we get a ruling on this one? It's pretty straight forward
> > implementation exposing a useful attribute.  
> 
> Who needs this?  Why is this useful?  Why hasn't there been a need for
> exposing serial number in past decades, and suddenly we need it so
> desperately?
> 
> We probably wouldn't want to add this if there is only a single user that
> needs this, especially give that userspace tools like lspci already expose
> this when someone needs it.
> 
> Also, we were reluctant to expose some types of information, like serial
> numbers and such, via the VPD recently, so why exposing any serial numbers
> via sysfs would be any different?

I'll note that we already expose these serial numbers for CXL type3 devices
because they are really useful when you have a bunch of identical devices
as they turn in RAS error records and other places.

I pushed back on adding this same sysfs attribute to other CXL types
on basis we could just get it from the associated PCI device (assuming this
series lands).

https://elixir.bootlin.com/linux/v6.17-rc5/source/drivers/cxl/core/memdev.c#L113

Note that we don't do is_visible magic for this particular attribute in CXL
because it is mandated as present by the CXL spec.  We do that for a lot
of other stuff though as it keeps the interface clean.

Jonathan


> 
> Thank you,
> 
> 	Krzysztof


  reply	other threads:[~2025-09-15 10:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21 23:22 [RESEND PATCH v7 0/1] PCI/sysfs: Expose PCIe device serial number Matthew Wood
2025-08-21 23:22 ` [RESEND PATCH v7 1/1] " Matthew Wood
2025-08-22  0:04   ` Keith Busch
2025-08-27  1:34   ` Hans Zhang
2025-08-27 19:39   ` Keith Busch
2025-09-12 16:56     ` Keith Busch
2025-09-13  6:17     ` Krzysztof Wilczyński
2025-09-15 10:03       ` Jonathan Cameron [this message]
2025-09-15 14:28       ` Keith Busch
2025-09-13  6:20   ` Krzysztof Wilczyński
2025-09-15 22:23     ` Keith Busch
2025-09-16 13:53       ` Jonathan Cameron
2025-09-15 19:39   ` Bjorn Helgaas
2025-09-16 22:35     ` Keith Busch
2025-09-17  8:34       ` Krzysztof Wilczyński
2025-09-17  8:52         ` Thomas Weißschuh
2025-09-17 12:16           ` Krzysztof Wilczyński
2025-09-17  9:08         ` Matthew Wood
2025-09-17 12:17           ` Krzysztof Wilczyński
2025-09-17  8:36     ` Krzysztof Wilczyński
  -- strict thread matches above, loose matches on Subject: below --
2025-08-11 17:39 [RESEND PATCH v7 0/1] " Matthew Wood
2025-08-11 17:39 ` [RESEND PATCH v7 1/1] " Matthew Wood

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=20250915110320.0000602f@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=bhelgaas@google.com \
    --cc=kbusch@kernel.org \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=superm1@kernel.org \
    --cc=thepacketgeek@gmail.com \
    --cc=thomas.weissschuh@linutronix.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