Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 8 Aug 2016 15:02:33 -0600
From:      Sean Bruno <sbruno@freebsd.org>
To:        Sreekanth Rupavatharam <rupavath@juniper.net>
Cc:        "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, Jack Vogel <jfvogel@gmail.com>
Subject:   Re: Question about em_irq_fast
Message-ID:  <07f2b16a-8764-48c6-ebd4-1d6d2ce44442@freebsd.org>
In-Reply-To: <135A343D-5624-404F-8A18-94744395E5C4@juniper.net>
References:  <C1288B46-4477-4972-92FA-F6910B3FA568@juniper.net> <6dd67a05-d484-593f-98f2-60a062c0daa3@freebsd.org> <135A343D-5624-404F-8A18-94744395E5C4@juniper.net>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--Hemf9u0x2Ke4KgnsMF1HfOuWKvH64owOA
Content-Type: multipart/mixed; boundary="GwH2uGBks8WIpW6IJTnbROj7JpCNs7Nca"
From: Sean Bruno <sbruno@freebsd.org>
To: Sreekanth Rupavatharam <rupavath@juniper.net>
Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>,
 Jack Vogel <jfvogel@gmail.com>
Message-ID: <07f2b16a-8764-48c6-ebd4-1d6d2ce44442@freebsd.org>
Subject: Re: Question about em_irq_fast
References: <C1288B46-4477-4972-92FA-F6910B3FA568@juniper.net>
 <6dd67a05-d484-593f-98f2-60a062c0daa3@freebsd.org>
 <135A343D-5624-404F-8A18-94744395E5C4@juniper.net>
In-Reply-To: <135A343D-5624-404F-8A18-94744395E5C4@juniper.net>

--GwH2uGBks8WIpW6IJTnbROj7JpCNs7Nca
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable



On 08/08/16 13:14, Sreekanth Rupavatharam wrote:
>=20
>=20
> Thanks,
>=20
> -Sreekanth
>=20
>> On Aug 8, 2016, at 12:09 PM, Sean Bruno <sbruno@freebsd.org> wrote:
>>
>> Is this with the "lem" driver or the "em" driver under QEMU?
>>
> It's for lem driver under qemu. My question is mainly about there being=
 no specific bit for a packet received in this register or am I missing s=
omething here?
>=20
>> Look for "legacy" in the boot output of your VM.
>>
>> sean
>>
>=20

It sounds like QEMU is spamming packets and interrupts incorrectly as
normal hardware doesn't have this issue.

sean


--GwH2uGBks8WIpW6IJTnbROj7JpCNs7Nca--

--Hemf9u0x2Ke4KgnsMF1HfOuWKvH64owOA
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQF8BAEBCgBmBQJXqPNpXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx
MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5k7gkIAJovYzmAjNCzDugpPoHxCiQB
H+PpIQWVFAKXpwupfu2VTvVs/j7KLPzGSIirkLbq3WDZTAXMbwdvk/y54VEhg0kS
T8NBAi7W/kCCHQU8YhFArmA5dVEHwWDrjkCigydD+EFApafLl0/NuRsu/PDRWbze
XeiUQMDCc1DZ6RDmqLqY98TY4XXW5zK5r8MJbAkyZN6saoouNzlKfIta48Xx04i5
9KXF6gMFrljFYnC42qgAFokZABXNISqINvi8DWxq7mFdMn3euQq9P/ORJOoPbkP9
6hq/58lSZsMQ0F2xhUjuIj0oOuuJvfyi5Jr/NHHMF3yweWk4YTPCMlXVjAtPGzg=
=+Mcc
-----END PGP SIGNATURE-----

--Hemf9u0x2Ke4KgnsMF1HfOuWKvH64owOA--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?07f2b16a-8764-48c6-ebd4-1d6d2ce44442>