------- Comment From boris.m...@de.ibm.com 2025-03-25 06:12 EDT-------
Solution  (provided by <schne...@linux.ibm.com>):

The first part of the problem is solved by not ignoring PFs in
standby. The second issue is solved by explicitly checking if
the parent PF of a given VF is configured and enabled. Since
a PFn can only have child VFs while enabled this is always the
case if this configuration has the parent PF.

Reproduction:  The first part of the issue can be reproduced by putting a PF
in standby, then reboot, configure it and try creating child VFs
which then appear in their own PCI domains. For the second part
two LPARs with both PFs+VFs from a single card sharing candidate
lists are required. Then a VF with its parent PF in the other
LPAR will incorrectly be placed in the shared PCI domain of
its "uncle PF".

Upstream-ID:   dc287e4c9149ab54a5003b4d4da007818b5fda3d
05793884a1f30509e477de9da233ab73584b1c8c
2844ddbd540fc84d7571cca65d6c43088e4d6952

Preventive:    yes

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2104120

Title:
  [Ubuntu 25.04] s390/pci: Fix PCHID per port multi-function detection

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:   s390/pci: Fix PCHID per port multi-function detection

  Symptom:       There are two cases in which PCI functions are incorrectly
                 placed, or not placed, in a shared PCI topology. In the first
                 case a PCI physical function (PF) which is initially in standby
                 was incorrectly not creating a new PCI topology when 
hotplugged,
                 but would if configured during boot. In the second case a PCI
                 virtual function (VF) would be placed in the shared PCI 
topology
                 of a PF if that PF is from the same card even if the parent PF
                 is not in the configuration which should lead the VF to be
                 isolated in its own single function topology.

  Problem:       Both problems are caused by logic bugs in the determination of
                 which PCI functions create topologies and when a PCI function
                 may be added to an existing topology.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2104120/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to