From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Alex Williamson <alex.williamson@redhat.com>,
Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org
Subject: Re: [PATCH v3 4/4] drivers/vfio: Enable VFIO if EEH is not supported
Date: Wed, 06 Aug 2014 23:05:43 +1000 [thread overview]
Message-ID: <53E22827.2000204@ozlabs.ru> (raw)
In-Reply-To: <1407329433.316.80.camel@ul30vt.home>
On 08/06/2014 10:50 PM, Alex Williamson wrote:
> On Wed, 2014-08-06 at 19:49 +1000, Gavin Shan wrote:
>> From: Alexey Kardashevskiy <aik@ozlabs.ru>
>>
>> The existing vfio_pci_open() fails upon error returned from
>> vfio_spapr_pci_eeh_open(), which breaks POWER7's P5IOC2 PHB
>> support which this patch brings back.
>>
>> The patch fixes the issue by dropping the return value of
>> vfio_spapr_pci_eeh_open().
>>
>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>> Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
>> ---
>> v3: Drop return value of vfio_spapr_pci_eeh_open()
>> ---
>> drivers/vfio/pci/vfio_pci.c | 6 +-----
>> drivers/vfio/vfio_spapr_eeh.c | 4 ++--
>> include/linux/vfio.h | 5 ++---
>> 3 files changed, 5 insertions(+), 10 deletions(-)
>>
>> diff --git a/drivers/vfio/pci/vfio_pci.c b/drivers/vfio/pci/vfio_pci.c
>> index e2ee80f..32d69c8 100644
>> --- a/drivers/vfio/pci/vfio_pci.c
>> +++ b/drivers/vfio/pci/vfio_pci.c
>> @@ -178,11 +178,7 @@ static int vfio_pci_open(void *device_data)
>> if (ret)
>> goto error;
>>
>> - ret = vfio_spapr_pci_eeh_open(vdev->pdev);
>> - if (ret) {
>> - vfio_pci_disable(vdev);
>> - goto error;
>> - }
>> + vfio_spapr_pci_eeh_open(vdev->pdev);
>> }
>>
>> return 0;
>> diff --git a/drivers/vfio/vfio_spapr_eeh.c b/drivers/vfio/vfio_spapr_eeh.c
>> index 4779cac..86dfceb 100644
>> --- a/drivers/vfio/vfio_spapr_eeh.c
>> +++ b/drivers/vfio/vfio_spapr_eeh.c
>> @@ -19,9 +19,9 @@
>> #define DRIVER_DESC "VFIO IOMMU SPAPR EEH"
>>
>> /* We might build address mapping here for "fast" path later */
>> -int vfio_spapr_pci_eeh_open(struct pci_dev *pdev)
>> +void vfio_spapr_pci_eeh_open(struct pci_dev *pdev)
>> {
>> - return eeh_dev_open(pdev);
>> + eeh_dev_open(pdev);
>
> Wasn't there some intent to provide a warning message, that would now be
> done here? Has that idea been dropped?
Comrade Gavin just forgot it :)
Gavin, please add it. Thanks!
>
>> }
>> EXPORT_SYMBOL_GPL(vfio_spapr_pci_eeh_open);
>>
>> diff --git a/include/linux/vfio.h b/include/linux/vfio.h
>> index 224128a..d320411 100644
>> --- a/include/linux/vfio.h
>> +++ b/include/linux/vfio.h
>> @@ -100,15 +100,14 @@ extern long vfio_external_check_extension(struct vfio_group *group,
>>
>> struct pci_dev;
>> #ifdef CONFIG_EEH
>> -extern int vfio_spapr_pci_eeh_open(struct pci_dev *pdev);
>> +extern void vfio_spapr_pci_eeh_open(struct pci_dev *pdev);
>> extern void vfio_spapr_pci_eeh_release(struct pci_dev *pdev);
>> extern long vfio_spapr_iommu_eeh_ioctl(struct iommu_group *group,
>> unsigned int cmd,
>> unsigned long arg);
>> #else
>> -static inline int vfio_spapr_pci_eeh_open(struct pci_dev *pdev)
>> +static inline void vfio_spapr_pci_eeh_open(struct pci_dev *pdev)
>> {
>> - return 0;
>> }
>>
>> static inline void vfio_spapr_pci_eeh_release(struct pci_dev *pdev)
>
>
>
--
Alexey
next prev parent reply other threads:[~2014-08-06 13:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 9:49 [PATCH v3 0/4] drivers/vfio: EEH Compile and compatibility Gavin Shan
2014-08-06 9:49 ` [PATCH v3 1/4] powerpc/eeh: Export eeh_iommu_group_to_pe() Gavin Shan
2014-08-06 9:49 ` [PATCH v3 2/4] drivers/vfio: Fix EEH build error Gavin Shan
2014-08-06 9:49 ` [PATCH v3 3/4] drivers/vfio: Allow EEH to be built as module Gavin Shan
2014-08-06 9:49 ` [PATCH v3 4/4] drivers/vfio: Enable VFIO if EEH is not supported Gavin Shan
2014-08-06 12:50 ` Alex Williamson
2014-08-06 13:05 ` Alexey Kardashevskiy [this message]
2014-08-07 2:10 ` Gavin Shan
2014-08-07 2:46 ` Gavin Shan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53E22827.2000204@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).