From: Rusty Russell <rusty@rustcorp.com.au>
To: Jason Wang <jasowang@redhat.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, qemu-devel@nongnu.org,
mst@redhat.com, Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: [PATCH] virtio-spec: clarify ro/rw bits and updating rule of virtio-net status field
Date: Tue, 20 Mar 2012 21:35:18 +1030 [thread overview]
Message-ID: <87ty1jpm6p.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20120320062020.12815.61342.stgit@jason-ThinkPad-T400>
On Tue, 20 Mar 2012 14:20:21 +0800, Jason Wang <jasowang@redhat.com> wrote:
> This patch clarifies VIRTIO_NET_S_LINK_UP as a read-only bit and
> VIRTIO_NET_S_ANNOUNCE as a read-writable bit. Also introduce the write 1 to
> clear semantics for all read-writable bits of config status field. This could
> help to reduce the config status field updating race between host and guest and
> also simplify the implementation.
>
> Signed-off-by: Jason Wang <jasowang@redhat.com>
This approach assumes an active config field, which neither lguest nor
S/390 have.
Thanks,
Rusty.
--
How could I marry someone with more hair than me? http://baldalex.org
next prev parent reply other threads:[~2012-03-20 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 6:20 [PATCH] virtio-spec: clarify ro/rw bits and updating rule of virtio-net status field Jason Wang
2012-03-20 11:05 ` Rusty Russell [this message]
2012-03-20 22:48 ` Michael S. Tsirkin
2012-03-20 23:40 ` Rusty Russell
2012-03-21 6:37 ` Michael S. Tsirkin
2012-03-22 4:30 ` Rusty Russell
2012-03-23 2:57 ` [Qemu-devel] " Jason Wang
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=87ty1jpm6p.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=borntraeger@de.ibm.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--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