Re: [PATCH 2/4] s390/pci: track whether util_str is valid in the zpci_dev

2020-09-22 Thread Matthew Rosato
On 9/21/20 5:41 AM, Niklas Schnelle wrote: Hi Matthew, On 9/19/20 5:28 PM, Matthew Rosato wrote: We'll need to keep track of whether or not the byte string in util_str is valid and thus needs to be passed to a vfio-pci passthrough device. Signed-off-by: Matthew Rosato --- arch/s390/include/

Re: [PATCH 2/4] s390/pci: track whether util_str is valid in the zpci_dev

2020-09-21 Thread Niklas Schnelle
Hi Matthew, On 9/19/20 5:28 PM, Matthew Rosato wrote: > We'll need to keep track of whether or not the byte string in util_str is > valid and thus needs to be passed to a vfio-pci passthrough device. > > Signed-off-by: Matthew Rosato > --- > arch/s390/include/asm/pci.h | 3 ++- > arch/s390/pci/

Re: [PATCH 2/4] s390/pci: track whether util_str is valid in the zpci_dev

2020-09-21 Thread Christian Borntraeger
On 19.09.20 17:28, Matthew Rosato wrote: > We'll need to keep track of whether or not the byte string in util_str is > valid and thus needs to be passed to a vfio-pci passthrough device. > > Signed-off-by: Matthew Rosato If this goes via the vfio tree, Acked-by: Christian Borntraeger (ple

[PATCH 2/4] s390/pci: track whether util_str is valid in the zpci_dev

2020-09-19 Thread Matthew Rosato
We'll need to keep track of whether or not the byte string in util_str is valid and thus needs to be passed to a vfio-pci passthrough device. Signed-off-by: Matthew Rosato --- arch/s390/include/asm/pci.h | 3 ++- arch/s390/pci/pci_clp.c | 1 + 2 files changed, 3 insertions(+), 1 deletion(-)