From: Eric Blake <eblake@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Cc: Prasad J Pandit <pjp@fedoraproject.org>,
Jason Wang <jasowang@redhat.com>, Li Qiang <liq3ea@gmail.com>,
Li Qiang <pangpei.lq@antfin.com>,
Sven Schnelle <svens@stackframe.org>,
Helge Deller <deller@gmx.de>, Ziming Zhang <ezrakiez@gmail.com>
Subject: Re: [RFC PATCH 3/3] hw/net/tulip: Set descriptor error bit when lenght is incorrect
Date: Fri, 24 Apr 2020 09:26:45 -0500 [thread overview]
Message-ID: <b1efc0fc-c8e2-10ba-31d4-db4baf73ab34@redhat.com> (raw)
In-Reply-To: <20200423231644.15786-4-f4bug@amsat.org>
On 4/23/20 6:16 PM, Philippe Mathieu-Daudé wrote:
> When a frame lenght is incorrect, set the RDES0 'Error Summary'
length (here, and in the subject)
> and 'Frame too long' bits. Then stop the receive process and
> trigger an abnormal interrupt. See [4.3.5 Receive Process].
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-04-24 14:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 23:16 [RFC PATCH 0/3] hw/net/tulip: Fix LP#1874539 Philippe Mathieu-Daudé
2020-04-23 23:16 ` [RFC PATCH 1/3] hw/net/tulip: Fix 'Descriptor Error' definition Philippe Mathieu-Daudé
2020-04-23 23:16 ` [RFC PATCH 2/3] hw/net/tulip: Log descriptor overflows Philippe Mathieu-Daudé
2020-04-23 23:16 ` [RFC PATCH 3/3] hw/net/tulip: Set descriptor error bit when lenght is incorrect Philippe Mathieu-Daudé
2020-04-24 2:16 ` Jason Wang
2020-04-24 13:42 ` Helge Deller
2020-04-24 14:26 ` Eric Blake [this message]
2020-04-24 15:27 ` [RFC PATCH 0/3] hw/net/tulip: Fix LP#1874539 Helge Deller
2020-04-26 2:49 ` Jason Wang
2020-04-26 7:57 ` Peter Maydell
2020-04-27 3:32 ` Jason Wang
2020-05-12 7:13 ` Philippe Mathieu-Daudé
2020-05-13 2:18 ` 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=b1efc0fc-c8e2-10ba-31d4-db4baf73ab34@redhat.com \
--to=eblake@redhat.com \
--cc=deller@gmx.de \
--cc=ezrakiez@gmail.com \
--cc=f4bug@amsat.org \
--cc=jasowang@redhat.com \
--cc=liq3ea@gmail.com \
--cc=pangpei.lq@antfin.com \
--cc=pjp@fedoraproject.org \
--cc=qemu-devel@nongnu.org \
--cc=svens@stackframe.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).