[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f49512dd-9a5c-b1d8-1609-da55e270635b@nvidia.com>
Date: Thu, 11 Feb 2021 17:47:23 +0200
From: Max Gurtovoy <mgurtovoy@...dia.com>
To: Jason Gunthorpe <jgg@...dia.com>, Cornelia Huck <cohuck@...hat.com>
CC: Alex Williamson <alex.williamson@...hat.com>,
Matthew Rosato <mjrosato@...ux.ibm.com>, <kvm@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <liranl@...dia.com>,
<oren@...dia.com>, <tzahio@...dia.com>, <leonro@...dia.com>,
<yarong@...dia.com>, <aviadye@...dia.com>, <shahafs@...dia.com>,
<artemp@...dia.com>, <kwankhede@...dia.com>, <ACurrid@...dia.com>,
<gmataev@...dia.com>, <cjia@...dia.com>, <yishaih@...dia.com>,
<aik@...abs.ru>
Subject: Re: [PATCH 8/9] vfio/pci: use x86 naming instead of igd
On 2/2/2021 7:10 PM, Jason Gunthorpe wrote:
> On Tue, Feb 02, 2021 at 05:06:59PM +0100, Cornelia Huck wrote:
>
>> On the other side, we have the zdev support, which both requires s390
>> and applies to any pci device on s390.
> Is there a reason why CONFIG_VFIO_PCI_ZDEV exists? Why not just always
> return the s390 specific data in VFIO_DEVICE_GET_INFO if running on
> s390?
>
> It would be like returning data from ACPI on other platforms.
Agree.
all agree that I remove it ?
we already have a check in the code:
if (ret && ret != -ENODEV) {
pci_warn(vdev->vpdev.pdev, "Failed to
setup zPCI info capabilities\n");
return ret;
}
so in case its not zdev we should get -ENODEV and continue in the good flow.
>
> It really seems like part of vfio-pci-core
>
> Jason
Powered by blists - more mailing lists