qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, Jes.Sorensen@redhat.com,
	Juan Quintela <quintela@redhat.com>,
	agraf@suse.de, stefanha@linux.vnet.ibm.com
Subject: [Qemu-devel] Re: [PATCH] e1000: clear EOP for multi-buffer descriptors
Date: Mon, 07 Feb 2011 08:37:15 -0700	[thread overview]
Message-ID: <1297093035.3518.5.camel@x201> (raw)
In-Reply-To: <20110207123026.GA18830@redhat.com>

On Mon, 2011-02-07 at 14:30 +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(-)
> 
> diff --git a/hw/e1000.c b/hw/e1000.c
> index 3427ff3..7853c12 100644
> --- a/hw/e1000.c
> +++ b/hw/e1000.c
> @@ -694,6 +694,9 @@ e1000_receive(VLANClientState *nc, const uint8_t *buf, size_t size)
>                  desc.length = cpu_to_le16(desc_size + fcs_len(s));
>                  desc.status |= E1000_RXD_STAT_EOP | E1000_RXD_STAT_IXSM;
>              } else {
> +                /* Guest zeroing out status is not a hardware requirement.
> +                   Clear EOP in case guest didn't do it. */
> +                desc.status &= ~E1000_RXD_STAT_EOP;
>                  desc.length = cpu_to_le16(desc_size);
>              }
>          } else { // as per intel docs; skip descriptors with null buf addr

Acked-by: Alex Williamson <alex.williamson@redhat.com>

  parent reply	other threads:[~2011-02-07 15: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
2011-02-07 15:37 ` Alex Williamson [this message]
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=1297093035.3518.5.camel@x201 \
    --to=alex.williamson@redhat.com \
    --cc=Jes.Sorensen@redhat.com \
    --cc=agraf@suse.de \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=stefanha@linux.vnet.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 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).