From: David Gibson <david@gibson.dropbear.id.au>
To: Greg Kurz <groug@kaod.org>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
"Alex Williamson" <alex.williamson@redhat.com>,
"Marcel Apfelbaum" <marcel@redhat.com>,
"Cédric Le Goater" <clg@kaod.org>
Subject: Re: [Qemu-devel] [PATCH for-4.0 0/2] spapr: Fix extended config space accesses
Date: Tue, 2 Apr 2019 09:52:14 +1100 [thread overview]
Message-ID: <20190401225214.GA9231@umbus.fritz.box> (raw)
In-Reply-To: <155414129703.574858.5054152366329409898.stgit@bahia.lan>
[-- Attachment #1: Type: text/plain, Size: 1832 bytes --]
On Mon, Apr 01, 2019 at 07:54:57PM +0200, Greg Kurz wrote:
> Recent commit c2077e2ca0da7 added stricter checks that now prevent
> a guest to access the extended config space of a PCIe device connected
> attached to a PHB on a pseries machine.
>
> PAPR compatible PHBs act like legacy PCI busses, but they do allow access
> to the full 4k config space of PCIe devices. As discussed several times on
> the list ([1] and [2]), we cannot really change PAPR PHB to have a true
> PCIe root bus since it would call for massive and unwanted changes in
> libvirt.
>
> This series tries to address the issue with a new PCI bus class method
> that tells if the PCI bus supports extended config space accesses,
> instead of relying on pci_bus_is_express() which wants a PCIe root bus.
> A new legacy PCI bus type is added to implement the PAPR behaviour.
>
> Note that this fixes a potential 4.0 regression, hence the for-4.0 tag.
>
> [1] https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg07377.html
> https://lists.gnu.org/archive/html/qemu-devel/2016-11/msg02839.html
>
> [2] https://lists.gnu.org/archive/html/qemu-ppc/2017-01/msg00034.html
So, I actually had some patches I'd been working on that address both
the c2077e2ca0da7 issue and the PAPR fixup in what I think is a
cleaner manner. Can't remember now if I posted and they got lost, or
I didn't get around to posting.
Nonetheless, at this point we're fixing a real regression on PAPR.
I'll look at cleaning this up post 4.0.
Reviewed-by: David Gibson <david@gibson.dropbe
I can take this through my tree if people are ok with that.
--
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: 833 bytes --]
next prev parent reply other threads:[~2019-04-01 23:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 17:54 [Qemu-devel] [PATCH for-4.0 0/2] spapr: Fix extended config space accesses Greg Kurz
2019-04-01 17:55 ` [Qemu-devel] [PATCH for-4.0 1/2] pci: Allow PCI bus subtypes to support " Greg Kurz
2019-04-01 17:55 ` [Qemu-devel] [PATCH for-4.0 2/2] spapr_pci: Fix " Greg Kurz
2019-04-01 19:25 ` [Qemu-devel] [PATCH for-4.0 0/2] spapr: " Alex Williamson
2019-04-01 22:52 ` David Gibson [this message]
2019-04-08 3:50 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2019-04-08 3:50 ` David Gibson
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=20190401225214.GA9231@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=alex.williamson@redhat.com \
--cc=clg@kaod.org \
--cc=groug@kaod.org \
--cc=marcel@redhat.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).