From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, Jes.Sorensen@redhat.com,
Alex Williamson <alex.williamson@redhat.com>,
agraf@suse.de, Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] Re: [PATCH] e1000: clear EOP for multi-buffer descriptors
Date: Mon, 7 Feb 2011 13:36:36 +0000 [thread overview]
Message-ID: <20110207133636.GA14542@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <20110207123026.GA18830@redhat.com>
On Mon, Feb 07, 2011 at 02:30:26PM +0200, Michael S. Tsirkin wrote:
> The e1000 spec says: if software statically allocates
> buffers, and uses memory read to check for completed descriptors, it
> simply has to zero the status byte in the descriptor to make it ready
> for reuse by hardware. This is not a hardware requirement (moving the
> hardware tail pointer is), but is necessary for performing an in–memory
> scan.
>
> Thus the guest does not have to clear the status byte. In case it
> doesn't we need to clear EOP for all descriptors
> except the last. While I don't know of any such guests,
> it's probably a good idea to stick to the spec.
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> Reported-by: Juan Quintela <quintela@redhat.com>
>
> ---
> hw/e1000.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
This makes sense: if the guest didn't clear the end-of-packet bit but
we're receiving a multi-buffer packet, clear EOP for all but the last
descriptor.
Reviewed-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
next prev parent reply other threads:[~2011-02-07 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 12:30 [Qemu-devel] [PATCH] e1000: clear EOP for multi-buffer descriptors Michael S. Tsirkin
2011-02-07 12:32 ` [Qemu-devel] " Juan Quintela
2011-02-07 13:36 ` Stefan Hajnoczi [this message]
2011-02-07 15:37 ` Alex Williamson
2011-02-07 17:59 ` Alex Williamson
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=20110207133636.GA14542@stefanha-thinkpad.localdomain \
--to=stefanha@linux.vnet.ibm.com \
--cc=Jes.Sorensen@redhat.com \
--cc=agraf@suse.de \
--cc=alex.williamson@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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 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).