From: Laszlo Ersek <lersek@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] virtio-net: add feature bit for any header s/g
Date: Thu, 11 Jul 2013 15:54:02 +0200 [thread overview]
Message-ID: <51DEB8FA.8080109@redhat.com> (raw)
In-Reply-To: <20130711134101.GA15676@redhat.com>
On 07/11/13 15:41, Michael S. Tsirkin wrote:
> So we'll add a way for users to shoot themselves in the foot
> by setting a flag incorrectly. Point being?
Point taken. The flag name being global / universal relates to the
concept, not support level. Exposing it in any device enables the user
to set the flag, which in turn enables the guest to negotiate it, and to
create descriptor chains that qemu doesn't recognize.
Thanks
Laszlo
prev parent reply other threads:[~2013-07-11 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 13:15 [Qemu-devel] [PATCH] virtio-net: add feature bit for any header s/g Michael S. Tsirkin
2013-07-11 13:39 ` Laszlo Ersek
2013-07-11 13:41 ` Michael S. Tsirkin
2013-07-11 13:54 ` Laszlo Ersek [this message]
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=51DEB8FA.8080109@redhat.com \
--to=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
/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).