From: Alex Williamson <alex.williamson@redhat.com>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, kvm-ppc@vger.kernel.org,
kvm@vger.kernel.org, david@gibson.dropbear.id.au
Subject: Re: [PATCH 0/2] VFIO: Accept IOMMU group (PE) ID
Date: Fri, 18 Sep 2015 15:47:32 +0000 [thread overview]
Message-ID: <1442591252.23936.254.camel@redhat.com> (raw)
In-Reply-To: <1442557469-22185-1-git-send-email-gwshan@linux.vnet.ibm.com>
On Fri, 2015-09-18 at 16:24 +1000, Gavin Shan wrote:
> This allows to accept IOMMU group (PE) ID from the parameter from userland
> when handling EEH operation so that the operation only affects the target
> IOMMU group (PE). If the IOMMU group (PE) ID in the parameter from userland
> is invalid, all IOMMU groups (PEs) attached to the specified container are
> affected as before.
>
> Gavin Shan (2):
> drivers/vfio: Support EEH API revision
> drivers/vfio: Support IOMMU group for EEH operations
>
> drivers/vfio/vfio_iommu_spapr_tce.c | 50 ++++++++++++++++++++++++++++++++++---
> drivers/vfio/vfio_spapr_eeh.c | 46 ++++++++++++++++++++++------------
> include/linux/vfio.h | 13 +++++++---
> include/uapi/linux/vfio.h | 6 +++++
> 4 files changed, 93 insertions(+), 22 deletions(-)
This interface is terrible. A function named foo_enabled() should
return a bool, yes or no, don't try to overload it to also return a
version. AFAICT, patch 2/2 breaks current users by changing the offset
of the union in struct vfio_eeh_pe_err. Also, we generally pass group
file descriptors rather than a group ID because we can prove the
ownership of the group through the file descriptor and we don't need to
worry about races with the group because we can hold a reference to it.
WARNING: multiple messages have this Message-ID (diff)
From: Alex Williamson <alex.williamson@redhat.com>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, kvm-ppc@vger.kernel.org,
kvm@vger.kernel.org, david@gibson.dropbear.id.au
Subject: Re: [PATCH 0/2] VFIO: Accept IOMMU group (PE) ID
Date: Fri, 18 Sep 2015 09:47:32 -0600 [thread overview]
Message-ID: <1442591252.23936.254.camel@redhat.com> (raw)
In-Reply-To: <1442557469-22185-1-git-send-email-gwshan@linux.vnet.ibm.com>
On Fri, 2015-09-18 at 16:24 +1000, Gavin Shan wrote:
> This allows to accept IOMMU group (PE) ID from the parameter from userland
> when handling EEH operation so that the operation only affects the target
> IOMMU group (PE). If the IOMMU group (PE) ID in the parameter from userland
> is invalid, all IOMMU groups (PEs) attached to the specified container are
> affected as before.
>
> Gavin Shan (2):
> drivers/vfio: Support EEH API revision
> drivers/vfio: Support IOMMU group for EEH operations
>
> drivers/vfio/vfio_iommu_spapr_tce.c | 50 ++++++++++++++++++++++++++++++++++---
> drivers/vfio/vfio_spapr_eeh.c | 46 ++++++++++++++++++++++------------
> include/linux/vfio.h | 13 +++++++---
> include/uapi/linux/vfio.h | 6 +++++
> 4 files changed, 93 insertions(+), 22 deletions(-)
This interface is terrible. A function named foo_enabled() should
return a bool, yes or no, don't try to overload it to also return a
version. AFAICT, patch 2/2 breaks current users by changing the offset
of the union in struct vfio_eeh_pe_err. Also, we generally pass group
file descriptors rather than a group ID because we can prove the
ownership of the group through the file descriptor and we don't need to
worry about races with the group because we can hold a reference to it.
next prev parent reply other threads:[~2015-09-18 15:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 6:24 [PATCH 0/2] VFIO: Accept IOMMU group (PE) ID Gavin Shan
2015-09-18 6:24 ` Gavin Shan
2015-09-18 6:24 ` [PATCH 1/2] drivers/vfio: Support EEH API revision Gavin Shan
2015-09-18 6:24 ` Gavin Shan
2015-09-18 6:24 ` [PATCH 2/2] drivers/vfio: Support IOMMU group for EEH operations Gavin Shan
2015-09-18 6:24 ` Gavin Shan
2015-09-18 15:47 ` Alex Williamson [this message]
2015-09-18 15:47 ` [PATCH 0/2] VFIO: Accept IOMMU group (PE) ID Alex Williamson
2015-09-19 6:22 ` David Gibson
2015-09-19 6:22 ` David Gibson
2015-09-21 1:42 ` David Gibson
2015-09-21 1:42 ` David Gibson
2015-09-21 5:21 ` Gavin Shan
2015-09-21 5:21 ` Gavin Shan
2015-09-21 12:11 ` Gavin Shan
2015-09-21 12:11 ` Gavin Shan
2015-09-21 16:41 ` Alex Williamson
2015-09-21 16:41 ` Alex Williamson
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=1442591252.23936.254.camel@redhat.com \
--to=alex.williamson@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=gwshan@linux.vnet.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.