[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YHUujU1o6bdHDfmS@unreal>
Date: Tue, 13 Apr 2021 08:39:25 +0300
From: Leon Romanovsky <leon@...nel.org>
To: Niklas Schnelle <schnelle@...ux.ibm.com>
Cc: Narendra K <narendra_k@...l.com>,
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: Re: [PATCH 0/1] Use of /sys/bus/pci/devices/…/index for non-SMBIOS platforms
On Mon, Apr 12, 2021 at 03:59:04PM +0200, Niklas Schnelle wrote:
> 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.
I'm missing an explanation that this change is safe for systemd and
they don't have some hard-coded assumption about the meaning of existing
index on s390.
Thanks
Powered by blists - more mailing lists