Date: Mon, 8 Aug 2016 17:22:05 -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: <86e67e5c-7b32-6cc7-02f1-a0227e12e674@freebsd.org> In-Reply-To: <523AA4A9-BBF0-40D2-A98E-6C608AC1C11F@juniper.net> References: <C1288B46-4477-4972-92FA-F6910B3FA568@juniper.net> <6dd67a05-d484-593f-98f2-60a062c0daa3@freebsd.org> <135A343D-5624-404F-8A18-94744395E5C4@juniper.net> <07f2b16a-8764-48c6-ebd4-1d6d2ce44442@freebsd.org> <523AA4A9-BBF0-40D2-A98E-6C608AC1C11F@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) --cSF4RNtGpOXc6Q8B48xKeLhtr9Eag2DKg Content-Type: multipart/mixed; boundary="vrQf16iBuNh1cJJKcel4IMV9EJQkS6dQW" 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: <86e67e5c-7b32-6cc7-02f1-a0227e12e674@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> <07f2b16a-8764-48c6-ebd4-1d6d2ce44442@freebsd.org> <523AA4A9-BBF0-40D2-A98E-6C608AC1C11F@juniper.net> In-Reply-To: <523AA4A9-BBF0-40D2-A98E-6C608AC1C11F@juniper.net> --vrQf16iBuNh1cJJKcel4IMV9EJQkS6dQW Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 08/08/16 15:40, Sreekanth Rupavatharam wrote: > Quite possibly, but my question remains. If the register doesn=E2=80=99= t have any specific value for just a received packet(no other events), ho= w is a value of 0 considered to be wrong? Or to flip the question around,= what should be the value of the register for just receive of a packet? >=20 > Thanks, >=20 > -Sreekanth >=20 >=20 > On 8/8/16, 2:02 PM, "Sean Bruno" <sbruno@freebsd.org> wrote: >=20 > It sounds like QEMU is spamming packets and interrupts incorrectly = as > normal hardware doesn't have this issue. >=20 As far as I can tell from the data sheets, the value should be non-zero. If its zero, then something has gone awry. Looking at the various spec sheets for various compatible devices, on a rx interrupt, we should see RXQ0 or TXQ0 set. sean --vrQf16iBuNh1cJJKcel4IMV9EJQkS6dQW-- --cSF4RNtGpOXc6Q8B48xKeLhtr9Eag2DKg 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 iQF8BAEBCgBmBQJXqRQeXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kM0AH/1R5RW+fFPkurFCWW3qRQd6q NwIJMGo7+q4myZ/yHaK5QFUG3B6aTXJ4XLYyNt8UQMqtrQfGfRyHwHxXhmnEPjJS HapvkE1pGuK9A1lYyazgAC5Y9xJxZ2EZi2Z9B2r2jYmMvK6Bmd4CkMxxxsdxpX+v lkX2zRRFlRrSlL7W08tXd52Xz2ITtNWlX4yXcHhXwBwH9ePMKlZvsYhpH3F3AIth 3i+FoISrvQ5sDCsSUY+0h1d8XwQywwPmY8mlJdO5aYk0lAfUwNJ19wAkrzphm0l/ qRDuetgxESJvQH5NVyVR0+NDGAuPxL0OdWovLHCFpuq2QtxOSYXFXzwBLq4owlA= =y4Eg -----END PGP SIGNATURE----- --cSF4RNtGpOXc6Q8B48xKeLhtr9Eag2DKg--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86e67e5c-7b32-6cc7-02f1-a0227e12e674>