From: Bin Meng <bmeng.cn@gmail.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Bin Meng <bin.meng@windriver.com>,
Christina Wang <christina.wang@windriver.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Markus Carlstedt <markus.carlstedt@windriver.com>
Subject: Re: [PATCH v2 1/3] hw/net: e1000: Correct the initial value of VET register
Date: Tue, 13 Jul 2021 07:06:56 +0800 [thread overview]
Message-ID: <CAEUhbmWZ3D50J08T5bCFAu_hStQ7n=T8O48OVaTAbrdLh48FbQ@mail.gmail.com> (raw)
In-Reply-To: <CAEUhbmWqU=sM6s1ogQB6vQmBSf6KrobW9xUcWCbt2aaO3OtuOg@mail.gmail.com>
On Mon, Jul 5, 2021 at 1:57 PM Bin Meng <bmeng.cn@gmail.com> wrote:
>
> On Mon, Jul 5, 2021 at 12:21 PM Jason Wang <jasowang@redhat.com> wrote:
> >
> >
> > 在 2021/7/2 下午5:24, Bin Meng 写道:
> > > From: Christina Wang <christina.wang@windriver.com>
> > >
> > > The initial value of VLAN Ether Type (VET) register is 0x8100, as per
> > > the manual and real hardware.
> > >
> > > While Linux e1000 driver always writes VET register to 0x8100, it is
> > > not always the case for everyone. Drivers relying on the reset value
> > > of VET won't be able to transmit and receive VLAN frames in QEMU.
> > >
> > > Reported-by: Markus Carlstedt <markus.carlstedt@windriver.com>
> > > Signed-off-by: Christina Wang <christina.wang@windriver.com>
> > > Signed-off-by: Bin Meng <bin.meng@windriver.com>
> > > ---
> > >
> > > (no changes since v1)
> > >
> > > hw/net/e1000.c | 2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> > > diff --git a/hw/net/e1000.c b/hw/net/e1000.c
> > > index 4f75b44cfc..20cbba6411 100644
> > > --- a/hw/net/e1000.c
> > > +++ b/hw/net/e1000.c
> > > @@ -29,6 +29,7 @@
> > > #include "hw/pci/pci.h"
> > > #include "hw/qdev-properties.h"
> > > #include "migration/vmstate.h"
> > > +#include "net/eth.h"
> > > #include "net/net.h"
> > > #include "net/checksum.h"
> > > #include "sysemu/sysemu.h"
> > > @@ -254,6 +255,7 @@ static const uint32_t mac_reg_init[] = {
> > > [MANC] = E1000_MANC_EN_MNG2HOST | E1000_MANC_RCV_TCO_EN |
> > > E1000_MANC_ARP_EN | E1000_MANC_0298_EN |
> > > E1000_MANC_RMCP_EN,
> > > + [VET] = ETH_P_VLAN,
> >
> >
> > I wonder if we need a compat flag for this, since we change the behavior.
> >
> > (See e1000_properties[])
> >
>
> No we don't need to since it does not break migration.
Ping?
next prev parent reply other threads:[~2021-07-12 23:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 9:24 [PATCH v2 1/3] hw/net: e1000: Correct the initial value of VET register Bin Meng
2021-07-02 9:24 ` [PATCH v2 2/3] hw/net: e1000e: " Bin Meng
2021-07-02 9:24 ` [PATCH v2 3/3] hw/net: e1000e: Don't zero out the VLAN tag in the legacy RX descriptor Bin Meng
2021-07-05 4:21 ` [PATCH v2 1/3] hw/net: e1000: Correct the initial value of VET register Jason Wang
2021-07-05 5:57 ` Bin Meng
2021-07-12 23:06 ` Bin Meng [this message]
2021-07-13 7:03 ` Jason Wang
2021-07-13 8:36 ` Bin Meng
2021-07-13 9:02 ` Jason Wang
2021-07-13 9:11 ` Bin Meng
2021-07-14 3:10 ` Jason Wang
2021-07-14 3:42 ` Bin Meng
2021-07-14 4:53 ` Jason Wang
2021-07-14 6:04 ` Bin Meng
2021-07-14 8:40 ` Jason Wang
2021-07-14 9:05 ` Bin Meng
2021-07-14 9:17 ` Jason Wang
2021-07-14 9:00 ` Peter Maydell
2021-07-14 9:14 ` Bin Meng
2021-07-14 9:24 ` 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='CAEUhbmWZ3D50J08T5bCFAu_hStQ7n=T8O48OVaTAbrdLh48FbQ@mail.gmail.com' \
--to=bmeng.cn@gmail.com \
--cc=bin.meng@windriver.com \
--cc=christina.wang@windriver.com \
--cc=jasowang@redhat.com \
--cc=markus.carlstedt@windriver.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).