qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: aik@ozlabs.ru, benh@kernel.crashing.org
Cc: agraf@suse.de, qemu-devel@nongnu.org, gwshan@au1.ibm.com,
	mdroth@linux.vnet.ibm.com, alex.williamson@redhat.com,
	qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 00/12] Allow EEH on spapr-pci-host-bridge devices
Date: Fri, 26 Feb 2016 22:33:24 +1100	[thread overview]
Message-ID: <20160226113324.GC24457@voom.redhat.com> (raw)
In-Reply-To: <1456486323-8047-1-git-send-email-david@gibson.dropbear.id.au>

[-- Attachment #1: Type: text/plain, Size: 2047 bytes --]

On Fri, Feb 26, 2016 at 10:31:51PM +1100, David Gibson wrote:
> For historical reasons, the spapr machine type has two PCI host bridge
> implementations: spapr-pci-host-bridge, and
> spapr-vfio-pci-host-bridge.  The latter was (duh) designed for VFIO
> devices, but later reworks mean it's not necessary for that, and VFIO
> can be used on the regular host bridge.
> 
> The only remaining difference is that EEH (Enhanced Error Handling -
> IBM's interface with similar purpose to AER) is only supported on the
> spapr-vfio-pci-host-bridge device.
> 
> This series corrects this, allowing EEH operations on the regular host
> bridge.  That allows the special VFIO host bridge (we leave a stub,
> for backwards compatibility).
> 
> EEH is only supported for VFIO devices, for the time being, and due to
> bugs in the kernel implementation, it is only usable when the host
> bridge only has devices from a single (host-side) IOMMU group
> ("Partitionable Endpoint", in IBM terminology).  That's an annoying
> limitation which we hope to lift someday, but it's no worse than now,
> since the spapr-vfio-pci-host-bridge only permits devices from a
> single IOMMU group in any case (although it doesn't properly enforce
> that).
> 
> I wrote these a while back, and I'm not sure why they got sidelined -
> I suspect I was looking for testing from Gavin Shan, not realising
> then that he was no longer working on EEH.  In any case, I'm hoping we
> can squeeze this change into 2.6, so we don't need to carry the broken
> spapr-vfio-pci-host-bridge device any longer.

Btw, Alexey.  Sorry, I know this will conflict with your vfio-ddw
patches.  However, from my brief glance at those, it looked like you
removed spapr-vfio-pci-host-bridge without properly fixing up EEH on
the regular host bridge, which I'd like to avoid.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2016-02-26 11:32 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 11:31 [Qemu-devel] [PATCH 00/12] Allow EEH on spapr-pci-host-bridge devices David Gibson
2016-02-26 11:31 ` [Qemu-devel] [PATCH 01/12] vfio: Start improving VFIO/EEH interface David Gibson
2016-02-29  0:58   ` Alexey Kardashevskiy
2016-02-29  3:13     ` David Gibson
2016-02-26 11:31 ` [Qemu-devel] [PATCH 02/12] spapr_pci: Switch to vfio_eeh_as_op() interface David Gibson
2016-02-29  1:43   ` Alexey Kardashevskiy
2016-02-29  3:00     ` David Gibson
2016-02-26 11:31 ` [Qemu-devel] [PATCH 03/12] spapr_pci: Eliminate class callbacks David Gibson
2016-02-29  1:43   ` Alexey Kardashevskiy
2016-02-29  3:42     ` Alexey Kardashevskiy
2016-02-26 11:31 ` [Qemu-devel] [PATCH 04/12] spapr_pci: Fold spapr_phb_vfio_eeh_configure() into spapr_pci code David Gibson
2016-02-29  1:43   ` Alexey Kardashevskiy
2016-02-29  3:45     ` Alexey Kardashevskiy
2016-02-29  4:25       ` Alexey Kardashevskiy
2016-02-29  6:20         ` David Gibson
2016-02-26 11:31 ` [Qemu-devel] [PATCH 05/12] spapr_pci: Fold spapr_phb_vfio_eeh_reset() " David Gibson
2016-02-29  1:43   ` Alexey Kardashevskiy
2016-02-26 11:31 ` [Qemu-devel] [PATCH 06/12] spapr_pci: Fold spapr_phb_vfio_eeh_get_state() " David Gibson
2016-02-29  1:43   ` Alexey Kardashevskiy
2016-02-26 11:31 ` [Qemu-devel] [PATCH 07/12] spapr_pci: Fold spapr_phb_vfio_eeh_set_option() " David Gibson
2016-02-29  1:44   ` Alexey Kardashevskiy
2016-02-26 11:31 ` [Qemu-devel] [PATCH 08/12] spapr_pci: Fold spapr_phb_vfio_reset() " David Gibson
2016-02-29  1:44   ` Alexey Kardashevskiy
2016-02-26 11:32 ` [Qemu-devel] [PATCH 09/12] spapr_pci: Allow EEH on spapr-pci-host-bridge David Gibson
2016-02-29  1:44   ` Alexey Kardashevskiy
2016-02-26 11:32 ` [Qemu-devel] [PATCH 10/12] spapr_pci: (Mostly) remove spapr-pci-vfio-host-bridge David Gibson
2016-02-29  1:42   ` Alexey Kardashevskiy
2016-02-29  3:06     ` David Gibson
2016-02-26 11:32 ` [Qemu-devel] [PATCH 11/12] spapr_pci: Remove finish_realize hook David Gibson
2016-02-29  1:44   ` Alexey Kardashevskiy
2016-02-26 11:32 ` [Qemu-devel] [PATCH 12/12] vfio: Eliminate vfio_container_ioctl() David Gibson
2016-02-29  1:44   ` Alexey Kardashevskiy
2016-02-26 11:33 ` David Gibson [this message]

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=20160226113324.GC24457@voom.redhat.com \
    --to=david@gibson.dropbear.id.au \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=alex.williamson@redhat.com \
    --cc=benh@kernel.crashing.org \
    --cc=gwshan@au1.ibm.com \
    --cc=mdroth@linux.vnet.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).