virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
	virtualization <virtualization@lists.linux-foundation.org>,
	Sasha Levin <levinsasha928@gmail.com>, kvm <kvm@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: virtio-pci new configuration proposal
Date: Tue, 08 Nov 2011 20:51:38 +1030	[thread overview]
Message-ID: <87vcqurk25.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20111108063249.GB11577@redhat.com>

On Tue, 8 Nov 2011 08:32:50 +0200, "Michael S. Tsirkin" <mst@redhat.com> 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?  Were the ppc guys right that's it's obsolescent?

Because PIO is going to be ugly AFAICT for every non-x86 platform.

Cheers,
Rusty.

  reply	other threads:[~2011-11-08 10:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 18:49 virtio-pci new configuration proposal Sasha Levin
2011-11-02 19:08 ` Michael S. Tsirkin
2011-11-02 19:07   ` Sasha Levin
2011-11-02 19:14     ` Michael S. Tsirkin
2011-11-03  1:58 ` Rusty Russell
     [not found] ` <8762j2t19l.fsf@rustcorp.com.au>
2011-11-03  8:33   ` Sasha Levin
2011-11-03 12:46     ` Michael S. Tsirkin
2011-11-03 13:19       ` Sasha Levin
2011-11-03 13:48         ` Michael S. Tsirkin
2011-11-04  9:44     ` Rusty Russell
     [not found]     ` <87lirwrzlg.fsf@rustcorp.com.au>
2011-11-04 11:40       ` Michael S. Tsirkin
     [not found]       ` <20111104114033.GA21308@redhat.com>
2011-11-04 12:32         ` Sasha Levin
2011-11-04 13:51           ` Michael S. Tsirkin
     [not found]           ` <20111104135113.GA24452@redhat.com>
2011-11-04 13:53             ` Sasha Levin
     [not found]             ` <1320414804.3334.13.camel@lappy>
2011-11-04 14:23               ` Michael S. Tsirkin
     [not found]               ` <20111104142338.GB24452@redhat.com>
2011-11-04 14:53                 ` Sasha Levin
2011-11-06  7:30                   ` Michael S. Tsirkin
2011-11-06 20:24                     ` Sasha Levin
2011-11-06 21:38                       ` Michael S. Tsirkin
2011-11-07  5:16                         ` Rusty Russell
2011-11-07 21:14                           ` Michael S. Tsirkin
2011-11-07 23:53                             ` Rusty Russell
2011-11-08  6:32                               ` Michael S. Tsirkin
2011-11-08 10:21                                 ` Rusty Russell [this message]
2011-11-08 21:31                                   ` Michael S. Tsirkin
2011-11-08 14:15                               ` Sasha Levin
2011-11-03 11:03   ` 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=87vcqurk25.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.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).