[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210412135905.1434249-1-schnelle@linux.ibm.com>
Date: Mon, 12 Apr 2021 15:59:04 +0200
From: Niklas Schnelle <schnelle@...ux.ibm.com>
To: Narendra K <narendra_k@...l.com>
Cc: Viktor Mihajlovski <mihajlov@...ux.ibm.com>,
Stefan Raspl <raspl@...ux.ibm.com>,
Peter Oberparleiter <oberpar@...ux.ibm.com>,
linux-netdev@...r.kernel.org, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-s390@...r.kernel.org
Subject: [PATCH 0/1] Use of /sys/bus/pci/devices/…/index for non-SMBIOS platforms
Hi Narendra, Hi All,
According to Documentation/ABI/testing/sysfs-bus-pci you are responsible
for the index device attribute that is used by systemd to create network
interface names.
Now we would like to reuse this attribute for firmware provided PCI
device index numbers on the s390 architecture which doesn't have
SMBIOS/DMI nor ACPI. All code changes are within our architecture
specific code but I'd like to get some Acks for this reuse. I've sent an
RFC version of this patch on 15th of March with the subject:
s390/pci: expose a PCI device's UID as its index
but got no response. Would it be okay to re-use this attribute for
essentially the same purpose but with index numbers provided by
a different platform mechanism? I think this would be cleaner than
further proliferation of /sys/bus/pci/devices/<dev>/xyz_index
attributes and allows re-use of the existing userspace infrastructure.
Thanks,
Niklas Schnelle
Niklas Schnelle (1):
s390/pci: expose a PCI device's UID as its index
Documentation/ABI/testing/sysfs-bus-pci | 11 +++++---
arch/s390/pci/pci_sysfs.c | 35 +++++++++++++++++++++++++
2 files changed, 42 insertions(+), 4 deletions(-)
--
2.25.1
Powered by blists - more mailing lists