Page MenuHomeFreeBSD

sfxge(4): ignore error in completion event on MCDIv2 HW
ClosedPublic

Authored by arybchik on Nov 21 2018, 11:23 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Feb 2, 7:29 PM
Unknown Object (File)
Jan 17 2025, 8:37 AM
Unknown Object (File)
Jan 9 2025, 12:21 PM
Unknown Object (File)
Jan 2 2025, 1:02 PM
Unknown Object (File)
Nov 26 2024, 9:49 AM
Unknown Object (File)
Nov 25 2024, 3:29 AM
Unknown Object (File)
Nov 24 2024, 11:37 PM
Unknown Object (File)
Nov 23 2024, 10:06 AM
Subscribers

Details

Summary

With MCDIv2, the reponse length can be to big to fit into the
CMDDONE_DATALEN field in the MCDI completion event. But rather that
the length being truncated, it can overflow into the CMDDONE_ERRNO
field (this is a longstanding firmware bug). Hence the CMDDONE_ERRNO
field may not be valid.

It isn't necessary to use the value in the CMDDONE_ERRNO field though,
so it can be ignored. The actual error code is already read from the
response header on MCDIv2 capable hardware and stored in emr_rc, so
that can be used instead.

Submitted by: Mark Spender <mspender at solarflare.com>
Sponsored by: Solarflare Communications, Inc.

Test Plan

amd64 tinderbox kernel builds tested
driver loaded/unloaded, interfaces up/down, traffic works fine

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision was not accepted when it landed; it landed in state Needs Review.Nov 23 2018, 4:00 PM
This revision was automatically updated to reflect the committed changes.