From: Alex Williamson <alex.williamson@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: aik@ozlabs.ru, qemu-devel@nongnu.org, gwshan@au1.ibm.com,
agraf@suse.de, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCHv3 1/7] vfio: Start improving VFIO/EEH interface
Date: Tue, 8 Mar 2016 18:36:48 -0700 [thread overview]
Message-ID: <20160308183648.04a76047@ul30vt.home> (raw)
In-Reply-To: <20160309005657.GF22546@voom.fritz.box>
On Wed, 9 Mar 2016 11:56:57 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> On Tue, Mar 08, 2016 at 11:33:45AM -0700, Alex Williamson wrote:
> > On Tue, 8 Mar 2016 13:10:23 +1100
> > David Gibson <david@gibson.dropbear.id.au> wrote:
> >
> > > At present the code handling IBM's Enhanced Error Handling (EEH) interface
> > > on VFIO devices operates by bypassing the usual VFIO logic with
> > > vfio_container_ioctl(). That's a poorly designed interface with unclear
> > > semantics about exactly what can be operated on.
> > >
> > > In particular it operates on a single vfio container internally (hence the
> > > name), but takes an address space and group id, from which it deduces the
> > > container in a rather roundabout way. groupids are something that code
> > > outside vfio shouldn't even be aware of.
> > >
> > > This patch creates new interfaces for EEH operations. Internally we
> > > have vfio_eeh_container_op() which takes a VFIOContainer object
> > > directly. For external use we have vfio_eeh_as_ok() which determines
> > > if an AddressSpace is usable for EEH (at present this means it has a
> > > single container with exactly one group attached), and vfio_eeh_as_op()
> > > which will perform an operation on an AddressSpace in the unambiguous case,
> > > and otherwise returns an error.
> > >
> > > This interface still isn't great, but it's enough of an improvement to
> > > allow a number of cleanups in other places.
> > >
> > > Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> > > Reviewed-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> > > ---
> >
> > I'll let you push this through your tree:
> >
> > Acked-by: Alex Williamson <alex.williamson@redhat.com>
>
> Thanks. Any guess at when your vGPU series will be pushed? Mine will
> conflict until that is merged upstream.
It's been out long enough, I'll send a pull request tomorrow. Thanks,
Alex
next prev parent reply other threads:[~2016-03-09 1:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 2:10 [Qemu-devel] [PATCHv3 0/7] Allow EEH on spapr-pci-host-bridge devices David Gibson
2016-03-08 2:10 ` [Qemu-devel] [PATCHv3 1/7] vfio: Start improving VFIO/EEH interface David Gibson
2016-03-08 18:33 ` Alex Williamson
2016-03-09 0:56 ` David Gibson
2016-03-09 1:36 ` Alex Williamson [this message]
2016-03-08 2:10 ` [Qemu-devel] [PATCHv3 2/7] spapr_pci: Switch to vfio_eeh_as_op() interface David Gibson
2016-03-08 2:10 ` [Qemu-devel] [PATCHv3 3/7] spapr_pci: Eliminate class callbacks David Gibson
2016-03-08 2:10 ` [Qemu-devel] [PATCHv3 4/7] spapr_pci: Allow EEH on spapr-pci-host-bridge David Gibson
2016-03-08 2:10 ` [Qemu-devel] [PATCHv3 5/7] spapr_pci: (Mostly) remove spapr-pci-vfio-host-bridge David Gibson
2016-03-08 2:10 ` [Qemu-devel] [PATCHv3 6/7] spapr_pci: Remove finish_realize hook David Gibson
2016-03-08 2:10 ` [Qemu-devel] [PATCHv3 7/7] vfio: Eliminate vfio_container_ioctl() David Gibson
2016-03-08 18:34 ` 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=20160308183648.04a76047@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=gwshan@au1.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).