qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH 8/9] eepro100: Pad received short frames
Date: Fri, 01 Apr 2011 19:40:18 +0200	[thread overview]
Message-ID: <4D960E02.2070208@mail.berlios.de> (raw)
In-Reply-To: <20110331214116.GC27264@redhat.com>

Am 31.03.2011 23:41, schrieb Michael S. Tsirkin:
> On Thu, Mar 31, 2011 at 10:33:30PM +0200, Stefan Weil wrote:
>> QEMU sends frames smaller than 60 bytes to ethernet nics.
>> This should be fixed in the networking code because normally
>> such frames are rejected by real NICs and their emulations.
>> To avoid this behaviour, other NIC emulations pad received
>> frames. This patch enables this workaround for eepro100, too.
>>
>> All related code is marked with CONFIG_PAD_RECEIVED_FRAMES,
>> so emulation of the correct handling for short frames can
>> be restored as soon as QEMU's networking code is fixed.
>>
>> Signed-off-by: Stefan Weil <weil@mail.berlios.de>
>
> qemu networking core isn't ethernet-specific
> (slirp is). That's why we don't do this in core,
> so the uglification isn't worth it.

Technically it is possible to add the padding needed for ethernet frames
in slirp code (a patch was already sent to qemu-devel) and any other
code location. Ethernet devices could also set a flag about their padding
requirements, so unnecessary padding could be avoided for non-ethernet
devices like virtio.

The last time when padding was discussed here, not everybody was happy
with the current solution: it was simply the solution which required
the least efforts.

I don't think that the current solution will last forever, simply
because it does not allow testing systems which do create short frames
because they want to test the reaction on short frames or for any
other reason.

That's why I want to be able to disable the padding in the device
emulation.


>
>> ---
>> hw/eepro100.c | 25 ++++++++++++++++++++++++-
>> 1 files changed, 24 insertions(+), 1 deletions(-)
>>
>> diff --git a/hw/eepro100.c b/hw/eepro100.c
>> index 500a3af..a740d2e 100644
>> --- a/hw/eepro100.c
>> +++ b/hw/eepro100.c
>> @@ -47,6 +47,14 @@
>> #include "eeprom93xx.h"
>> #include "sysemu.h"
>>
>> +/* QEMU sends frames smaller than 60 bytes to ethernet nics.
>> + * This should be fixed in the networking code because normally
>> + * such frames are rejected by real nics and their emulations.
>> + * To avoid this behaviour, other nic emulations pad received
>> + * frames. The following definition enables this workaround for
>> + * eepro100, too. */
>> +#define CONFIG_PAD_RECEIVED_FRAMES
>> +
>> #define KiB 1024
>>
>> /* Debug EEPRO100 card. */
>> @@ -1756,19 +1764,32 @@ static ssize_t nic_receive(VLANClientState 
>> *nc, const uint8_t * buf, size_t size
>> */
>> EEPRO100State *s = DO_UPCAST(NICState, nc, nc)->opaque;
>> uint16_t rfd_status = 0xa000;
>> +#if defined(CONFIG_PAD_RECEIVED_FRAMES)
>> + uint8_t min_buf[60];
>> +#endif
>> static const uint8_t broadcast_macaddr[6] =
>> { 0xff, 0xff, 0xff, 0xff, 0xff, 0xff };
>>
>> +#if defined(CONFIG_PAD_RECEIVED_FRAMES)
>> + /* Pad to minimum Ethernet frame length */
>> + if (size < sizeof(min_buf)) {
>> + memcpy(min_buf, buf, size);
>> + memset(&min_buf[size], 0, sizeof(min_buf) - size);
>> + buf = min_buf;
>> + size = sizeof(min_buf);
>> + }
>> +#endif
>> +
>> if (s->configuration[8] & 0x80) {
>> /* CSMA is disabled. */
>> logout("%p received while CSMA is disabled\n", s);
>> return -1;
>> +#if !defined(CONFIG_PAD_RECEIVED_FRAMES)
>> } else if (size < 64 && (s->configuration[7] & BIT(0))) {
>> /* Short frame and configuration byte 7/0 (discard short receive) set:
>> * Short frame is discarded */
>> logout("%p received short frame (%zu byte)\n", s, size);
>> s->statistics.rx_short_frame_errors++;
>> -#if 0
>> return -1;
>> #endif
>> } else if ((size > MAX_ETH_FRAME_SIZE + 4) && !(s->configuration[18] 
>> & BIT(3))) {
>> @@ -1847,9 +1868,11 @@ static ssize_t nic_receive(VLANClientState 
>> *nc, const uint8_t * buf, size_t size
>> "(%zu bytes); data truncated\n", rfd_size, size);
>> size = rfd_size;
>> }
>> +#if !defined(CONFIG_PAD_RECEIVED_FRAMES)
>> if (size < 64) {
>> rfd_status |= 0x0080;
>> }
>> +#endif
>> TRACE(OTHER, logout("command 0x%04x, link 0x%08x, addr 0x%08x, size 
>> %u\n",
>> rfd_command, rx.link, rx.rx_buf_addr, rfd_size));
>> stw_le_phys(s->ru_base + s->ru_offset + offsetof(eepro100_rx_t, status),
>> -- 
>> 1.7.2.5
>

  reply	other threads:[~2011-04-01 17:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31 20:33 [Qemu-devel] eepro100: Improve emulation and portability Stefan Weil
2011-03-31 20:33 ` [Qemu-devel] [PATCH 1/9] eepro100: Avoid duplicate debug messages Stefan Weil
2011-03-31 20:33 ` [Qemu-devel] [PATCH 2/9] eepro100: Fix endianness issues Stefan Weil
2011-03-31 21:52   ` [Qemu-devel] " Michael S. Tsirkin
2011-04-01 17:52     ` Stefan Weil
2011-04-03 11:40       ` Michael S. Tsirkin
2011-03-31 20:33 ` [Qemu-devel] [PATCH 3/9] eepro100: Support byte/word writes to port address Stefan Weil
2011-03-31 20:33 ` [Qemu-devel] [PATCH 4/9] eepro100: Support byte/word writes to pointer register Stefan Weil
2011-03-31 20:33 ` [Qemu-devel] [PATCH 5/9] eepro100: Support byte/word read/write access to MDI control register Stefan Weil
2011-03-31 20:33 ` [Qemu-devel] [PATCH 6/9] eepro100: Support byte read access to general " Stefan Weil
2011-03-31 20:33 ` [Qemu-devel] [PATCH 7/9] eepro100: Support 32 bit read access to flash register Stefan Weil
2011-03-31 20:33 ` [Qemu-devel] [PATCH 8/9] eepro100: Pad received short frames Stefan Weil
2011-03-31 21:41   ` [Qemu-devel] " Michael S. Tsirkin
2011-04-01 17:40     ` Stefan Weil [this message]
2011-03-31 20:33 ` [Qemu-devel] [PATCH 9/9] eepro100: Simplify receive data structure Stefan Weil

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=4D960E02.2070208@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=mst@redhat.com \
    --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).