From: David Gibson <david@gibson.dropbear.id.au>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: pair@us.ibm.com, "Daniel P. Berrangé" <berrange@redhat.com>,
aik@ozlabs.ru, groug@kaod.org, qemu-devel@nongnu.org,
paulus@samba.org, clg@kaod.org, mdroth@us.ibm.com,
qemu-ppc@nongnu.org
Subject: Re: [PATCH v3 1/2] spapr: Disable legacy virtio devices for pseries-5.0 and later
Date: Thu, 12 Mar 2020 12:14:20 +1100 [thread overview]
Message-ID: <20200312011420.GD711223@umbus.fritz.box> (raw)
In-Reply-To: <20200311030812-mutt-send-email-mst@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]
On Wed, Mar 11, 2020 at 03:11:16AM -0400, Michael S. Tsirkin wrote:
> On Wed, Mar 11, 2020 at 11:58:57AM +1100, David Gibson wrote:
> > Note that several things that I believe are now in the PCIe spec, but
> > really derive more from PC legacy considerations, don't apply at all
> > for PAPR. e.g. there's no meaningful distinction between integrated
> > and slotted devices, multiple independent host bridges is routine and
> > doesn't require any (virtual) hardware visible domain numbers.
>
> Domain numbers are a Linux thing, not a PCIe thing. On x86 they come
> from ACPI segment numbers. As such they aren't usually hardware
> visible on x86, they are supplied by firmware.
Oh, ok. I thought that at least on the standard IO 0xcf8 host bridge
controller the domain number was written into certain registers to
select the relevant root bus.
On POWER the domain numbers are arbitrarily assigned within Linux.
"Hardware" (well, the firmware/hypervisor) uses a different
identifier, called the BUID (generally a large, 64-bit pseudo-address)
in the device tree and hypercalls.
[As an aside, this means the use of domain numbers in libvirt XML is
complete bogosity]
--
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:[~2020-03-12 1:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 4:30 [PATCH v3 0/2] spapr: Use vIOMMU translation for virtio by default David Gibson
2020-03-05 4:30 ` [PATCH v3 1/2] spapr: Disable legacy virtio devices for pseries-5.0 and later David Gibson
2020-03-05 10:31 ` Greg Kurz
2020-03-10 9:43 ` Greg Kurz
2020-03-10 9:57 ` Michael S. Tsirkin
2020-03-10 11:03 ` Michael S. Tsirkin
2020-03-10 12:24 ` Greg Kurz
2020-03-10 11:56 ` Daniel P. Berrangé
2020-03-11 0:58 ` David Gibson
2020-03-11 7:11 ` Michael S. Tsirkin
2020-03-12 1:14 ` David Gibson [this message]
2020-03-12 6:41 ` Michael S. Tsirkin
2020-03-05 4:30 ` [PATCH v3 2/2] spapr: Enable virtio iommu_platform=on by default David Gibson
2020-03-05 11:59 ` Greg Kurz
2020-03-10 10:43 ` Greg Kurz
2020-03-12 4:14 ` Alexey Kardashevskiy
2020-03-12 8:02 ` Greg Kurz
2020-03-10 11:43 ` Upstream QEMU guest support policy ? Re: [PATCH v3 0/2] spapr: Use vIOMMU translation for virtio " Daniel P. Berrangé
2020-03-11 1:12 ` David Gibson
2020-03-11 7:33 ` Michael S. Tsirkin
2020-03-12 1:10 ` David Gibson
2020-03-12 6:32 ` Michael S. Tsirkin
2020-03-16 3:06 ` David Gibson
2020-03-11 10:01 ` Daniel P. Berrangé
2020-03-11 11:48 ` Michael S. Tsirkin
2020-03-12 1:09 ` David Gibson
2020-03-12 1:08 ` David Gibson
2020-03-12 9:47 ` Daniel P. Berrangé
2020-03-11 17:19 ` Greg Kurz
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=20200312011420.GD711223@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--cc=berrange@redhat.com \
--cc=clg@kaod.org \
--cc=groug@kaod.org \
--cc=mdroth@us.ibm.com \
--cc=mst@redhat.com \
--cc=pair@us.ibm.com \
--cc=paulus@samba.org \
--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 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.