From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>,
virtualization@lists.linux-foundation.org
Cc: habanero@linux.vnet.ibm.com, Shirley Ma <mashirle@us.ibm.com>,
Krishna Kumar2 <krkumar2@in.ibm.com>,
kvm@vger.kernel.org, steved@us.ibm.com,
Tom Lendacky <tahm@linux.vnet.ibm.com>,
borntraeger@de.ibm.com, avi@redhat.com,
bryanv@daemoninthecloset.org
Subject: Re: [PATCHv3] virtio-spec: 64 bit features, used/avail event, fixes
Date: Thu, 02 Jun 2011 11:19:35 +0930 [thread overview]
Message-ID: <87ei3dxas0.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20110601102548.GA11013@redhat.com>
On Wed, 1 Jun 2011 13:25:48 +0300, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> Add an option to modify the notificatin
> hand-off in virtio to be basically like Xen:
> each side published an index, the other side only triggers
> an event when it crosses that index value
> (Xen event indexes start at 1, ours start at 0 for
> backward-compatiblity, but that's minor).
>
> Since we've run out of bits in the 32 bit field,
> I added another 32 bit and bit 31 enables that.
OK. I've applied this, and published it as the 0.9 draft.
Thanks!
Rusty.
next prev parent reply other threads:[~2011-06-02 1:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 10:25 [PATCHv3] virtio-spec: 64 bit features, used/avail event, fixes Michael S. Tsirkin
2011-06-02 1:49 ` Rusty Russell [this message]
2011-08-03 16:05 ` Michael S. Tsirkin
2011-08-03 16:05 ` Michael S. Tsirkin
2011-08-03 16:15 ` Gerd Hoffmann
2011-08-03 16:15 ` Gerd Hoffmann
2011-08-03 16:29 ` Michael S. Tsirkin
2011-08-03 16:29 ` Michael S. Tsirkin
2011-08-03 16:39 ` Michael S. Tsirkin
2011-08-04 7:55 ` Gerd Hoffmann
2011-08-04 7:55 ` Gerd Hoffmann
2011-08-03 16:39 ` Michael S. Tsirkin
2011-06-02 1:49 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2011-06-01 10:25 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=87ei3dxas0.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=avi@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=bryanv@daemoninthecloset.org \
--cc=habanero@linux.vnet.ibm.com \
--cc=krkumar2@in.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mashirle@us.ibm.com \
--cc=mst@redhat.com \
--cc=steved@us.ibm.com \
--cc=tahm@linux.vnet.ibm.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 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.