On Wed, Oct 10, 2018 at 02:55:07PM +0200, Sebastian Ott wrote: > Hello Bjorn, > > On Wed, 12 Sep 2018, Bjorn Helgaas wrote: > > On Wed, Sep 12, 2018 at 02:34:09PM +0200, Sebastian Ott wrote: > > > On s390 we currently handle SRIOV within firmware. Which means > > > that the PF is under firmware control and not visible to operating > > > systems. SRIOV enablement happens within firmware and VFs are > > > passed through to logical partitions. > > > > > > I'm working on a new mode were the PF is under operating system > > > control (including SRIOV enablement). However we still need > > > firmware support to access the VFs. The way this is supposed > > > to work is that when firmware traps the SRIOV enablement it > > > will present machine checks to the logical partition that > > > triggered the SRIOV enablement and provide the VFs via hotplug > > > events. > > > > > > The problem I'm faced with is that the VF detection code in > > > sriov_enable leads to unusable functions in s390. > > > > We're moving away from the weak function implementation style. Can > > you take a look at Arnd's work here, which uses pci_host_bridge > > callbacks instead? > > > > https://lkml.kernel.org/r/20180817102645.3839621-1-arnd@xxxxxxxx > > What's the status of Arnd's patches - will they go upstream in the next > couple of versions? I hope so [1]. IIRC Arnd mentioned doing some minor updates, so I'm waiting on that. > What about my patches that I rebased on Arnd's branch > will they be considered? Definitely. From my point of view they're just lined up behind Arnd's patches. [1] https://lore.kernel.org/linux-pci/20181002205903.GD120535@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
