virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
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: Mon, 7 Nov 2011 23:14:14 +0200	[thread overview]
Message-ID: <20111107211413.GA11577@redhat.com> (raw)
In-Reply-To: <871utktsuw.fsf@rustcorp.com.au>

On Mon, Nov 07, 2011 at 03:46:23PM +1030, Rusty Russell wrote:
> On Sun, 6 Nov 2011 23:38:49 +0200, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> > On Sun, Nov 06, 2011 at 10:24:57PM +0200, Sasha Levin wrote:
> > > On Sun, 2011-11-06 at 09:30 +0200, Michael S. Tsirkin wrote:
> > > > On Fri, Nov 04, 2011 at 04:53:05PM +0200, Sasha Levin wrote:
> > > > > > I guess my assumption is that most options will be in use,
> > > > > > not discarded dead-ends.
> > > > > 
> > > > > I don't know about that. 64 bit features would be pretty rare for now -
> > > > > and I don't think that setting the alignment will be also enabled by
> > > > > default.
> 
> The truth is somewhere between.  New features tend to be used, and
> importantly, they have to be offered.
> 
> Anyway, the *per-device* config part will be contiguous.  So we're
> talking about pci-specific features.
> 
> So far, the only three things make sense to have in a capability list:
> MSI-X, the upper 32 feature bits, and the per-device config.
> 
> Thanks,
> Rusty.

You mean the queue # to MSI-X vector mapping?
One thing to remember is that it must be in the same type of BAR as
the queue selection, since by PCI rules MMIO writes aren't I think
ordered with PIO writes (it doesn't matter with KVM but might
with another hypervisor).

-- 
MST

  reply	other threads:[~2011-11-07 21:14 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 [this message]
2011-11-07 23:53                             ` Rusty Russell
2011-11-08  6:32                               ` Michael S. Tsirkin
2011-11-08 10:21                                 ` Rusty Russell
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=20111107211413.GA11577@redhat.com \
    --to=mst@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --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).