From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: virtio-pci new configuration proposal Date: Tue, 8 Nov 2011 23:31:50 +0200 Message-ID: <20111108213148.GA4504@redhat.com> References: <20111104142338.GB24452@redhat.com> <1320418385.3334.25.camel@lappy> <20111106073007.GA7146@redhat.com> <1320611097.3299.10.camel@lappy> <20111106213849.GA14292@redhat.com> <871utktsuw.fsf@rustcorp.com.au> <20111107211413.GA11577@redhat.com> <87aa87sd4y.fsf@rustcorp.com.au> <20111108063249.GB11577@redhat.com> <87vcqurk25.fsf@rustcorp.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <87vcqurk25.fsf@rustcorp.com.au> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Rusty Russell Cc: Anthony Liguori , virtualization , Sasha Levin , kvm , linux-kernel List-Id: virtualization@lists.linuxfoundation.org On Tue, Nov 08, 2011 at 08:51:38PM +1030, Rusty Russell wrote: > On Tue, 8 Nov 2011 08:32:50 +0200, "Michael S. Tsirkin" wrote: > > On Tue, Nov 08, 2011 at 10:23:33AM +1030, Rusty Russell wrote: > > > Even so, should we just use the PCI cap list, and have each > > > cap entry just contain a BIR & offset? > > > > > > Thanks, > > > Rusty. > > > > And size :) > > I say, Rusty, did you see my patch? That's what it's doing, > > I also addressed the issue that with KVM on x86, PIO is faster > > than MMIO so we need to use it for notifications/isr. > > Faster? Really? Why? I think, because it doesn't need to be emulated to get the address and the value. There are so many ways on x86 to do memory access, you need a lot of code to figure out what's going on. > Were the ppc guys right that's it's obsolescent? For PCI - surely not. PCI Express spec tries to discourage its usage. But support is there even in Express. > Because PIO is going to be ugly AFAICT for every non-x86 platform. > > Cheers, > Rusty. > So we should make the BAR MMIO on non-x86 host, PIO on x86. Guest should just map and use what it's given. -- MST