[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <871utktsuw.fsf@rustcorp.com.au>
Date: Mon, 07 Nov 2011 15:46:23 +1030
From: Rusty Russell <rusty@...tcorp.com.au>
To: "Michael S. Tsirkin" <mst@...hat.com>,
Sasha Levin <levinsasha928@...il.com>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
kvm <kvm@...r.kernel.org>,
virtualization <virtualization@...ts.linux-foundation.org>,
Anthony Liguori <anthony@...emonkey.ws>
Subject: Re: virtio-pci new configuration proposal
On Sun, 6 Nov 2011 23:38:49 +0200, "Michael S. Tsirkin" <mst@...hat.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists