On 1/21/21 6:28 PM, Greg Kroah-Hartman wrote:
> On Thu, Jan 21, 2021 at 06:04:52PM +0100, Niklas Schnelle wrote:
>>
>>
>> On 1/21/21 4:54 PM, Bjorn Helgaas wrote:
>>> [Greg may be able to help compare/contrast this s390 UID with udev
>>> persistent names]
>>>
>>> On Thu, Jan 21, 2021 at 04:31:55PM +0100, Niklas Schnelle wrote:
>>>> On 1/15/21 4:29 PM, Bjorn Helgaas wrote:
>>>>> On Fri, Jan 15, 2021 at 12:20:59PM +0100, Niklas Schnelle wrote:
>>>>>> On 1/14/21 5:14 PM, Greg Kroah-Hartman wrote:
>>>>>>> On Thu, Jan 14, 2021 at 04:51:17PM +0100, Niklas Schnelle wrote:
>>>>>>>> On 1/14/21 4:17 PM, Greg Kroah-Hartman wrote:
>>>>>>>>> On Thu, Jan 14, 2021 at 04:06:11PM +0100, Niklas Schnelle wrote:
>>>>>>>>>> On 1/14/21 2:58 PM, Greg Kroah-Hartman wrote:
>>>>>>>>>>> On Thu, Jan 14, 2021 at 02:44:53PM +0100, Christian Brauner wrote:
>>>>>>>>>>>> On Thu, Jan 14, 2021 at 02:20:10PM +0100, Niklas Schnelle wrote:
>>>>>>>>>>>>> On 1/13/21 7:55 PM, Bjorn Helgaas wrote:
>>>>>>>>>>>>>> On Wed, Jan 13, 2021 at 08:47:58AM +0100, Niklas Schnelle wrote:
>>>>>>>>>>>>>>> On 1/12/21 10:50 PM, Bjorn Helgaas wrote:
>>>>>> ... snip ...
>>>>>>
>>>>>>>
>>>>>>>> if (!zpci_global_kset)
>>>>>>>> return -ENOMEM;
>>>>>>>>
>>>>>>>> return sysfs_create_group(&zpci_global_kset->kobj, &zpci_attr_group_global);
>>>>>>>
>>>>>>> Huge hint, if in a driver, or bus subsystem, and you call sysfs_*,
>>>>>>> that's usually a huge clue that you are doing something wrong.
>>>>>>>
>>>>>>> Try the above again, with a simple attribute group, and name for it, and
>>>>>>> it should "just work".
>>>>>>
>>>>>> I'm probably missing something but I don't get how this could work
>>>>>> in this case. If I'm seeing this right the default attribute group
>>>>>> here is pci_bus_type.bus_groups and that is already set in
>>>>>> drivers/pci/pci-driver.c so I don't think I should set that.
>>>>>>
>>>>>> I did however find bus_create_file() which does work when using the
>>>>>> path /sys/bus/pci/uid_checking instead. This would work for us if
>>>>>> Bjorn is okay with that path and the code is really clean and simple
>>>>>> too.
>>>>>>
>>>>>> That said, I think we could also add something like
>>>>>> bus_create_group(). Then we could use that to also clean up
>>>>>> drivers/pci/slot.c:pci_slot_init() and get the original path
>>>>>> /sys/bus/pci/zpci/uid_checking.
>>>>>
>>>>> I don't think "uid_checking" is quite the right name. It says
>>>>> something about the *implementation*, but it doesn't convey what that
>>>>> *means* to userspace. IIUC this file tells userspace something about
>>>>> whether a given PCI device always has the same PCI domain/bus/dev/fn
>>>>> address (or maybe just the same domain?)
>>>>>
>>>>> It sounds like this feature could be useful beyond just s390, and
>>>>> other arches might implement it differently, without the UID concept.
>>>>> If so, I'm OK with something at the /sys/bus/pci/xxx level as long as
>>>>> the name is not s390-specific (and "uid" sounds s390-specific).
>>>>>
>>>>> I assume it would also help with the udev/systemd end if you could
>>>>> make this less s390 dependent.
>>>>
>>>> I've thought about this more and even implemented a proof of concept
>>>> patch for a global attribute using a pcibios_has_reproducible_addressing()
>>>> hook.
>>>>
>>>> However after implementing it I think as a more general and
>>>> future proof concept it makes more sense to do this as a per device
>>>> attribute, maybe as another flag in "stuct pci_dev" named something
>>>> like "reliable_address". My reasoning behind this can be best be seen
>>>> with a QEMU example. While I expect that QEMU can easily guarantee
>>>> that one can always use "0000:01:00.0" for a virtio-pci NIC and
>>>> thus enp1s0 interface name, the same might be harder to guarantee
>>>> for a SR-IOV VF passed through with vfio-pci in that same VM and
>>>> even less so if a thunderbolt controller is passed through and
>>>> enumeration may depend on daisy chaining. The QEMU example
>>>> also applies to s390 and maybe others will in the future.
>>>
>>> I'm a little wary of using the PCI geographical address
>>> ("0000:01:00.0") as a stable name. Even if you can make a way to use
>>> that to identify a specific device instance, regardless of how it is
>>> plugged in or passed through, it sounds like we could end up with
>>> "physical PCI addresses" and "virtual PCI addresses" that look the
>>> same and would cause confusion.
>>>
>>> This concept sounds similar to the udev concept of a "persistent
>>> device name". What advantages does this s390 UID have over the udev
>>> approach?
>>>
>>> There are optional PCI device serial numbers that we currently don't
>>> really make use of. Would that be a generic way to help with this?
>>>
>>
>> As far as I understand systemd/udev uses the PCI geographical address
>> by default ("enP<domain>p<bus>s<hotplug_slot_idx>...") for PCI attached
>> network interfaces in many cases and a lot of users have already built
>> their firewall/routing rules on these.
>
> Which is fine as "normally" that does not change. But on some machines,
> it is quite volatile so users pick a different naming scheme.
>
> And this is all done in userspace, I really don't understand what you
> want to do in the kernel here. If you want to expose another unique
> thing that the hardware knows about, wonderful, userspace can then use
> that if it wants to in how it names specific devices. But don't put
> that naming in the kernel, that's not where it belongs.
Oh no I definitely don't want to put any naming in the kernel.
Rather this is very much "a thing that the hardware knows".
The thing being:
We're a virtual platform and this PCI devices' address is generated
from user configuration and we guarantee it's stable.
>
>> Now taking this beyond s390 my idea is that under some circumstances
>> just as with UID Uniqueness for us, the platform can tell if a PCI
>> geographical address is a reliable identifier thus sytemd/udev
>> has more information about the quality of existing naming schemes
>> incorporating information from the geographical address.
>
> The platform does not "know" if this is reliable or not, sorry. That's
> not how PCI or UEFI works.
Yes I assumed as much which is why my examples were all about virtualized
platforms/hypervisors. I would say QEMU very much knows if the PCI address
is coming from its fluffy virtual sandbox or real wild hardware (pass-through).
>
>> Looking at my personal KVM guests (Ubuntu, Arch Linux, Ubuntu ARM64)
>> as well as my workstation (Arch Linux) all of them use a scheme
>> with parts of the geographical address.
>
> Because for the most part, yes, this works. Until you plug another
> device into the system. Or remove one. Or plug a hotplug device in and
> then cold boot with it plugged in (or removed). Or, my favorite system,
> just decide to renumber the PCI bus every other boot "just because".
>
> None of that variability can be known by the kernel, that's only known by
> the user of that system, so again, they can make the best decision as to
> how to name their devices. If you want to use the systemd default,
> wonderful, but know that it does not work for everyone, so systemd
> allows you to do whatever you want.
>
>> So in essence my idea is all about either choosing the best existing
>> default name or making sure we at least know if it may not be reliable.
>
> There is no reliability "score" here, sorry. Hardware is fun :)
Well as said above, at the very least there is real hardware, emulated
hardware and our always virtualizing machines that keep things cozy
and reliable enough that you can keep running OSs from the 70s largely
unchanged on >5 GHz CPUs. So I think at least our platform has a pretty
good track record in this regard.
>
> good luck!
>
> greg k-h
>
