All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	Carsten Otte <cotte@de.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	linux390@de.ibm.com, Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>"Michael S. Tsirkin"
	<mst@redhat.com>,
	lguest@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	linux-s390@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: Re: [RFC][PATCH] virtio: 64 bit features
Date: Tue, 12 Apr 2011 12:55:42 +0930	[thread overview]
Message-ID: <87ei58cfrd.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20110411165525.GA1395@redhat.com>

On Mon, 11 Apr 2011 19:55:25 +0300, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> Extend features to 64 bit so we can use more
> transport bits.
> 
> Future patches add two new feature bits which would
> exhaust the supply of transport feature bits,
> so let's add bit 31 to tell the guest that
> there are now 64 worth of features.
> 
> For PCI this also changes the config layout.
> 
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

This was pretty much the way I imagined it would work.  We need a patch
to the spec and a lot of cross testing...

Thanks!
Rusty.

WARNING: multiple messages have this Message-ID (diff)
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	Carsten Otte <cotte@de.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	linux390@de.ibm.com, Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	lguest@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	linux-s390@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: Re: [RFC][PATCH] virtio: 64 bit features
Date: Tue, 12 Apr 2011 12:55:42 +0930	[thread overview]
Message-ID: <87ei58cfrd.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20110411165525.GA1395@redhat.com>

On Mon, 11 Apr 2011 19:55:25 +0300, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> Extend features to 64 bit so we can use more
> transport bits.
> 
> Future patches add two new feature bits which would
> exhaust the supply of transport feature bits,
> so let's add bit 31 to tell the guest that
> there are now 64 worth of features.
> 
> For PCI this also changes the config layout.
> 
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

This was pretty much the way I imagined it would work.  We need a patch
to the spec and a lot of cross testing...

Thanks!
Rusty.

  reply	other threads:[~2011-04-12  3:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11 16:55 [RFC][PATCH] virtio: 64 bit features Michael S. Tsirkin
2011-04-12  3:25 ` Rusty Russell [this message]
2011-04-12  3:25   ` Rusty Russell
2011-04-12  3:25 ` Rusty Russell
2011-04-12 14:04 ` Christian Borntraeger
2011-04-12 14:45   ` Michael S. Tsirkin
2011-04-12 14:45   ` Michael S. Tsirkin
2011-04-12 14:04 ` Christian Borntraeger
  -- strict thread matches above, loose matches on Subject: below --
2011-04-11 16:55 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=87ei58cfrd.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=borntraeger@de.ibm.com \
    --cc=cotte@de.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux390@de.ibm.com \
    --cc=mst@redhat.com \
    --cc=schwidefsky@de.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.