qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Isaku Yamahata <yamahata@valinux.co.jp>,
	Alex Williamson <alex.williamson@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] PCI: Bus number from the bridge, not the device
Date: Mon, 22 Nov 2010 16:58:11 +0200	[thread overview]
Message-ID: <20101122145811.GM7948@redhat.com> (raw)
In-Reply-To: <20101122145616.GC30157@redhat.com>

On Mon, Nov 22, 2010 at 04:56:16PM +0200, Michael S. Tsirkin wrote:
> On Mon, Nov 22, 2010 at 04:52:32PM +0200, Gleb Natapov wrote:
> > On Mon, Nov 22, 2010 at 04:50:29PM +0200, Michael S. Tsirkin wrote:
> > > On Mon, Nov 22, 2010 at 03:04:51PM +0200, Gleb Natapov wrote:
> > > > On Mon, Nov 22, 2010 at 10:16:57AM +0200, Michael S. Tsirkin wrote:
> > > > > On Mon, Nov 22, 2010 at 09:37:07AM +0200, Gleb Natapov wrote:
> > > > > > > > > It's probably required to make them stable anyway.
> > > > > > > > > 
> > > > > > > > Why?
> > > > > > > 
> > > > > > > To avoid bus renumbering on reboot after you add a pci-to-pci bridge.
> > > > > > > 
> > > > > > Why should qemu care?
> > > > > 
> > > > > Stable bus numbering is a feature *users* care about, because
> > > > > some Guest OSes get confused when a card gets moved to another
> > > > > bus.
> > > > > 
> > > > So if user cares about it it should not change HW configuration of QEMU.
> > > > I guess those OSes knows how to handle hot-pluggable equipment otherwise
> > > > they will get confused on real HW too. Why QEMU should care to preserve
> > > > something in a face of configuration change?
> > > > 
> > > > --
> > > > 			Gleb.
> > > 
> > > We've been there, weren't we? See
> > > http://fedoraproject.org/wiki/Features/KVM_Stable_PCI_Addresses#KVM_Stable_PCI_Addresses
> > > 
> > This is about stable HW configuration.
> 
> Exactly. We have the same need for nested bridges and devices behind
> them.
> 
And now you are talking about topology, not guest assigned bus numbers.
So suddenly you are on my side? I don't even get what are you arguing
about at this point.

--
			Gleb.

  reply	other threads:[~2010-11-22 14:58 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04 21:53 [Qemu-devel] [PATCH] PCI: Bus number from the bridge, not the device Alex Williamson
2010-11-08 11:22 ` [Qemu-devel] " Michael S. Tsirkin
2010-11-08 14:52   ` Alex Williamson
2010-11-08 16:26     ` Michael S. Tsirkin
2010-11-08 16:36       ` Alex Williamson
2010-11-08 16:48         ` Michael S. Tsirkin
2010-11-08 17:00       ` Gleb Natapov
2010-11-08 17:08         ` Michael S. Tsirkin
2010-11-08 17:27           ` Gleb Natapov
2010-11-09  2:41       ` Isaku Yamahata
2010-11-09 11:53         ` Michael S. Tsirkin
2010-11-19 17:02           ` Markus Armbruster
2010-11-19 20:38             ` Gleb Natapov
2010-11-20 20:17               ` Michael S. Tsirkin
2010-11-21  8:32                 ` Gleb Natapov
2010-11-21  9:50                   ` Michael S. Tsirkin
2010-11-21 10:19                     ` Gleb Natapov
2010-11-21 11:53                       ` Michael S. Tsirkin
2010-11-21 12:50                         ` Gleb Natapov
2010-11-21 14:48                           ` Michael S. Tsirkin
2010-11-21 16:01                             ` Gleb Natapov
2010-11-21 16:38                               ` Michael S. Tsirkin
2010-11-21 17:28                                 ` Gleb Natapov
2010-11-21 18:22                               ` Michael S. Tsirkin
2010-11-21 19:29                                 ` Gleb Natapov
2010-11-21 20:39                                   ` Michael S. Tsirkin
2010-11-22  7:37                                     ` Gleb Natapov
2010-11-22  8:16                                       ` Michael S. Tsirkin
2010-11-22 13:04                                         ` Gleb Natapov
2010-11-22 14:50                                           ` Michael S. Tsirkin
2010-11-22 14:52                                             ` Gleb Natapov
2010-11-22 14:56                                               ` Michael S. Tsirkin
2010-11-22 14:58                                                 ` Gleb Natapov [this message]
2010-11-22 16:41                                                   ` Michael S. Tsirkin
2010-11-22 17:01                                                     ` Gleb Natapov
2010-12-13 20:04   ` Alex Williamson
2010-12-14  4:46     ` Michael S. Tsirkin
2010-12-14  4:49       ` Alex Williamson
2010-12-14  4:57         ` Michael S. Tsirkin
2010-12-14  5:04           ` Alex Williamson
2010-12-14 12:26             ` Michael S. Tsirkin
2010-12-14 18:34               ` Alex Williamson
2010-12-15  9:56                 ` Michael S. Tsirkin
2010-12-15 15:27                   ` Alex Williamson
2010-12-16  7:08                     ` Isaku Yamahata
2010-12-16  8:36                       ` Michael S. Tsirkin
2010-12-21 10:13                         ` Isaku Yamahata
2010-12-21 10:56                           ` 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=20101122145811.GM7948@redhat.com \
    --to=gleb@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=armbru@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yamahata@valinux.co.jp \
    /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).