qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <dwg@au1.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 5/8] pci: Replace pci_find_domain() with more general pci_root_bus_path()
Date: Thu, 23 May 2013 22:21:09 +1000	[thread overview]
Message-ID: <20130523122109.GD26259@boomeroo.fritz.box> (raw)
In-Reply-To: <20130523110407.GB17480@redhat.com>

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

On Thu, May 23, 2013 at 02:04:08PM +0300, Michael S. Tsirkin wrote:
> On Thu, May 09, 2013 at 10:31:09AM +1000, David Gibson wrote:
> > pci_find_domain() is used in a number of places where we want an id for a
> > whole PCI domain (i.e. the subtree under a PCI root bus).  The trouble is
> > that many platforms may support multiple independent host bridges with no
> > hardware supplied notion of domain number.
> > 
> > This patch, therefore, replaces calls to pci_find_domain() with calls to
> > a new pci_root_bus_path() returning a string.  The new call is implemented
> > in terms of a new callback in the host bridge class, so it can be defined
> > in some way that's well defined for the platform.  When no callback is
> > available we fall back on the qbus name.
> > 
> > Most current uses of pci_find_domain() are for error or informational
> > messages, so the change in identifiers should be harmless.  The exception
> > is pci_get_dev_path(), whose results form part of migration streams.  To
> > maintain compatibility with old migration streams, the PIIX PCI host is
> > altered to always supply "0000" for this path, which matches the old domain
> > number (since the code didn't actually support domains other than 0).
> > 
> > For the pseries (spapr) PCI bridge we use a different platform-unique
> > identifier (pseries machines can routinely have dozens of PCI host
> > bridges).  Theoretically that breaks migration streams, but given that we
> > don't yet have migration support for pseries, it doesn't matter.
> > 
> > Any other machines that have working migration support including PCI
> > devices will need to be updated to maintain migration stream compatibility.
> > 
> > Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> 
> AFAIK PC is the only one with working migration, yes, but
> we have Q35 as well which can be migrated.

Good point, I'll add a similar hook to q35.

-- 
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: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-05-23 13:04 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-09  0:31 [Qemu-devel] [0/8] Clean up PCI code to allow for multiple root buses David Gibson
2013-05-09  0:31 ` [Qemu-devel] [PATCH 1/8] pci: Cleanup configuration for pci-hotplug.c David Gibson
2013-05-23 11:11   ` Michael S. Tsirkin
2013-05-23 12:23     ` David Gibson
2013-05-24  7:44     ` David Gibson
2013-05-23 14:54   ` Paolo Bonzini
2013-05-24  7:46     ` David Gibson
2013-05-09  0:31 ` [Qemu-devel] [PATCH 2/8] pci: Move pci_read_devaddr to pci-hotplug-old.c David Gibson
2013-05-09  0:31 ` [Qemu-devel] [PATCH 3/8] pci: Abolish pci_find_root_bus() David Gibson
2013-05-23 11:26   ` Michael S. Tsirkin
2013-05-09  0:31 ` [Qemu-devel] [PATCH 4/8] pci: Use helper o find device's root bus in pci_find_domain() David Gibson
2013-05-09  0:31 ` [Qemu-devel] [PATCH 5/8] pci: Replace pci_find_domain() with more general pci_root_bus_path() David Gibson
2013-05-23 11:04   ` Michael S. Tsirkin
2013-05-23 12:21     ` David Gibson [this message]
2013-05-23 14:51     ` Paolo Bonzini
2013-05-23 14:57       ` Michael S. Tsirkin
2013-05-23 15:00         ` Paolo Bonzini
2013-05-23 15:06           ` Michael S. Tsirkin
2013-05-24  7:40           ` David Gibson
2013-05-09  0:31 ` [Qemu-devel] [PATCH 6/8] pci: Simpler implementation of primary PCI bus David Gibson
2013-05-23 11:01   ` Michael S. Tsirkin
2013-05-23 12:16     ` David Gibson
2013-05-23 14:39       ` Michael S. Tsirkin
2013-05-23 11:22   ` Michael S. Tsirkin
2013-05-23 12:16     ` David Gibson
2013-05-29  9:43       ` David Gibson
2013-05-29  9:47         ` David Gibson
2013-05-29  9:55         ` Michael S. Tsirkin
2013-05-29 10:06           ` David Gibson
2013-05-29 10:17             ` Michael S. Tsirkin
2013-05-29 11:04               ` David Gibson
2013-05-29 12:22                 ` Michael S. Tsirkin
2013-05-30  3:34                   ` David Gibson
2013-05-30  5:02                     ` Michael S. Tsirkin
2013-06-06  7:39                       ` David Gibson
2013-06-06  8:18                         ` Michael S. Tsirkin
2013-05-09  0:31 ` [Qemu-devel] [PATCH 7/8] pci: Remove domain from PCIHostBus David Gibson
2013-05-09  0:31 ` [Qemu-devel] [PATCH 8/8] pci: Fold host_buses list into PCIHostState functionality David Gibson
2013-05-14 10:53 ` [Qemu-devel] [0/8] Clean up PCI code to allow for multiple root buses Michael S. Tsirkin
2013-05-23 11:12 ` Michael S. Tsirkin

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=20130523122109.GD26259@boomeroo.fritz.box \
    --to=dwg@au1.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@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).