From: David Miller <davem@davemloft.net>
To: rdreier@cisco.com
Cc: drifter@bcsoft.de, netdev@vger.kernel.org
Subject: Re: e1000 under VMware doesn't work since 2.6.27.16 - BISECTED
Date: Fri, 20 Mar 2009 17:00:07 -0700 (PDT) [thread overview]
Message-ID: <20090320.170007.204645866.davem@davemloft.net> (raw)
In-Reply-To: <20090320.165516.112348262.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Fri, 20 Mar 2009 16:55:16 -0700 (PDT)
> From: Roland Dreier <rdreier@cisco.com>
> Date: Fri, 20 Mar 2009 16:03:58 -0700
>
> > > > we're using virtual machines under VMware with the e1000 emulated
> > > > network card.
> >
> > > Sounds like vmware doesn't emulate the e1000 accurately enough.
> >
> > I would consider problems with the vmware emulated e1000 to be similar
> > to hardware quirks in some other chip rev supported by the e1000
> > driver. If a driver change broke e1000 inside a vmware VM then we
> > should probably fix the kernel if possible (although vmware probably
> > wants to improve their emulation too).
>
> If such a "fix" would be to the detriment of real actual hardware,
> this logic doesn't hold.
>
> The same applies to cases like qemu as well.
And I want to amend this to state that I emphatically do not think
that a driver maintainer is on the hook to be compatible with
all the software emulators out there.
That's rediculious.
Keeping up with the problems on real hardware is difficult enough. At
the very least the software emulators can be fixed easily, whereas
real hardware not so much.
prev parent reply other threads:[~2009-03-21 0:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 16:41 e1000 under VMware doesn't work since 2.6.27.16 - BISECTED Jens Stroebel
2009-03-20 22:57 ` David Miller
2009-03-20 23:03 ` Roland Dreier
2009-03-20 23:55 ` David Miller
2009-03-21 0:00 ` David Miller [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=20090320.170007.204645866.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=drifter@bcsoft.de \
--cc=netdev@vger.kernel.org \
--cc=rdreier@cisco.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).