From: Jason Wang <jasowang@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, Dmitry Fleytman <dmitry@daynix.com>
Cc: Kevin Wolf <mail@kevin-wolf.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] e1000e: Don't zero out buffer address in rx descriptor
Date: Fri, 21 Oct 2016 10:01:30 +0800 [thread overview]
Message-ID: <f47c2ccb-ce0b-91d3-5a61-6c20614e2fb0@redhat.com> (raw)
In-Reply-To: <20161018142705.GK4706@noname.str.redhat.com>
On 2016年10月18日 22:27, Kevin Wolf wrote:
> Am 18.10.2016 um 16:10 hat Dmitry Fleytman geschrieben:
>> > 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!
> Thanks, Dmitry!
>
> I assume that your R-b implies that you don't send a pull request
> yourself. If so, what's the process for getting the patch merged? Is
> Jason going to pick it up normally or should I send a pull request of my
> own?
>
I've picked this in my tree.
Thanks
next prev parent reply other threads:[~2016-10-21 2:01 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 [this message]
2016-10-21 1:58 ` 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=f47c2ccb-ce0b-91d3-5a61-6c20614e2fb0@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).