From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: KVM call minutes 2013-01-29 - Port I/O Date: Fri, 1 Feb 2013 00:37:15 +0200 Message-ID: <20130131223715.GA18073@redhat.com> References: <1359579910.23274.31.camel@pasglop> <87a9rq5p0p.fsf@codemonkey.ws> <20130130222017.GE6544@redhat.com> <1359585125.23274.41.camel@pasglop> <20130130224919.GA8820@redhat.com> <1359586927.23274.62.camel@pasglop> <1359588510.11144.382.camel@bling.home> <20130131104921.GA520@redhat.com> <1359650043.2585.6.camel@ul30vt.home> <1359668654.15464.19.camel@pasglop> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: KVM devel mailing list , Juan Quintela , Alexander Graf , qemu-devel , Alex Williamson , Alon Levy , Gerd Hoffmann , Anthony Liguori , qemu-ppc , David Gibson , Andreas =?iso-8859-1?Q?F=E4rber?= , =?iso-8859-1?Q?Herv=E9?= Poussineau To: Benjamin Herrenschmidt Return-path: Content-Disposition: inline In-Reply-To: <1359668654.15464.19.camel@pasglop> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org > > Here's a more interesting example: > > > > -+-[0000:01]-+-00.0 NVIDIA Corporation GT218 [GeForce G210M] > > | \-00.1 NVIDIA Corporation High Definition Audio Controller > > \-[0000:00]-+-00.0 Intel Corporation Mobile 4 Series Chipset Memory Controller Hub > > +-01.0 Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port > > > > This system seems to have two host bridges with VGA behind each of them. > > There's no bridge to control VGA routing, so I don't know how the > > selection is done. It's possible the g210m never sees legacy VGA > > accesses in this mode. This bios has another mode which makes the g210m > > the primary graphics and hides the integrated graphics, essentially the > > same as I mention above with hiding integrated endpoint graphics when > > plugin graphics are used. Thanks, > > Wait, those are two different busses ... and there's no bridge ? Is that > the funky x86 multi domain crackpot where you have multiple roots with > non overlapping bus numbers in the same domain ? > > Ben. Domain numbering on x86 comes from firmware and you know what Linus said about firmware developers ... -- MST