qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Dmitry Fleytman <dmitry@daynix.com>, Kevin Wolf <mail@kevin-wolf.de>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] e1000e: Don't zero out buffer address in rx descriptor
Date: Fri, 21 Oct 2016 09:58:48 +0800	[thread overview]
Message-ID: <a191a373-c8d6-37d8-ea0d-66a61f99eced@redhat.com> (raw)
In-Reply-To: <E34ADA36-74A5-439D-9459-B5F753292CF9@daynix.com>



On 2016年10月18日 22:10, Dmitry Fleytman wrote:
>> On 17 Oct 2016, at 01:35 AM, Kevin Wolf <mail@kevin-wolf.de> wrote:
>>
>> The e1000e emulation zeroes out any used rx descriptor and then writes a
>> completely newly constructed value there. By doing this, it doesn't only
>> update the write-back area of the descriptors (as it's supposed to do),
>> but it also clears the buffer address, which real hardware doesn't do.
>>
>> The spec explicitly mentions in chapter 7.1.8 that it is valid for a
>> driver to reuse a descriptor and only update the status field while
>> doing so, i.e. reusing the old buffer address:
>>
>>     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 patch fixes the behaviour to leave the buffer address in
>> descriptors unchanged even after the descriptor has been used.
> Hi Kevin,
>
> Reviewed-by: Dmitry Fleytman <dmitry@daynix.com>
>
> Thanks for catching this!
>
> ~Dmitry

Applied, thanks.

>
>> Signed-off-by: Kevin Wolf <mail@kevin-wolf.de>
>> ---
>> hw/net/e1000e_core.c | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/hw/net/e1000e_core.c b/hw/net/e1000e_core.c
>> index 9fa4116..a5ca97d 100644
>> --- a/hw/net/e1000e_core.c
>> +++ b/hw/net/e1000e_core.c
>> @@ -1280,11 +1280,10 @@ e1000e_write_lgcy_rx_descr(E1000ECore *core, uint8_t *desc,
>>
>>      struct e1000_rx_desc *d = (struct e1000_rx_desc *) desc;
>>
>> -    memset(d, 0, sizeof(*d));
>> -
>>      assert(!rss_info->enabled);
>>
>>      d->length = cpu_to_le16(length);
>> +    d->csum = 0;
>>
>>      e1000e_build_rx_metadata(core, pkt, pkt != NULL,
>>                               rss_info,
>> @@ -1293,6 +1292,7 @@ e1000e_write_lgcy_rx_descr(E1000ECore *core, uint8_t *desc,
>>                               &d->special);
>>      d->errors = (uint8_t) (le32_to_cpu(status_flags) >> 24);
>>      d->status = (uint8_t) le32_to_cpu(status_flags);
>> +    d->special = 0;
>> }
>>
>> static inline void
>> @@ -1303,7 +1303,7 @@ e1000e_write_ext_rx_descr(E1000ECore *core, uint8_t *desc,
>> {
>>      union e1000_rx_desc_extended *d = (union e1000_rx_desc_extended *) desc;
>>
>> -    memset(d, 0, sizeof(*d));
>> +    memset(&d->wb, 0, sizeof(d->wb));
>>
>>      d->wb.upper.length = cpu_to_le16(length);
>>
>> @@ -1327,7 +1327,7 @@ e1000e_write_ps_rx_descr(E1000ECore *core, uint8_t *desc,
>>      union e1000_rx_desc_packet_split *d =
>>          (union e1000_rx_desc_packet_split *) desc;
>>
>> -    memset(d, 0, sizeof(*d));
>> +    memset(&d->wb, 0, sizeof(d->wb));
>>
>>      d->wb.middle.length0 = cpu_to_le16((*written)[0]);
>>
>> -- 
>> 2.1.4
>>

      parent reply	other threads:[~2016-10-21  1:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-16 22:35 [Qemu-devel] [PATCH] e1000e: Don't zero out buffer address in rx descriptor Kevin Wolf
2016-10-18 14:10 ` Dmitry Fleytman
2016-10-18 14:27   ` Kevin Wolf
2016-10-19  6:48     ` Dmitry Fleytman
2016-10-19  7:25       ` Kevin Wolf
2016-10-19  7:57         ` Dmitry Fleytman
2016-10-19 10:07           ` Kevin Wolf
2016-10-19 10:15             ` Dmitry Fleytman
2016-10-21  2:01     ` Jason Wang
2016-10-21  1:58   ` Jason Wang [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=a191a373-c8d6-37d8-ea0d-66a61f99eced@redhat.com \
    --to=jasowang@redhat.com \
    --cc=dmitry@daynix.com \
    --cc=kwolf@redhat.com \
    --cc=mail@kevin-wolf.de \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).