aboutsummaryrefslogtreecommitdiff
path: root/test/Transforms/LoopUnroll/runtime-loop.ll
diff options
context:
space:
mode:
authorKevin Bowling <kbowling@FreeBSD.org>2026-08-16 07:56:03 +0000
committerKevin Bowling <kbowling@FreeBSD.org>2026-08-16 10:21:15 +0000
commitc82a015ede8d49aabc8bb253b7597b8db0f42524 (patch)
tree13528fd6657e015a1cb926e0e83743235205ebd5 /test/Transforms/LoopUnroll/runtime-loop.ll
parent41a0f7a0a447ef2092faadb35f6d4c3f80c088bf (diff)
igc: Propagate hardware initialization failures
The reset helper discards igc_reset_hw and igc_init_hw errors. Runtime initialization then continues programming rings and filters, and iflib publishes the interface as running even though the controller did not reach a usable state. Initial attach similarly continues into NVM and MAC setup after a failed reset. Return errors from the reset helper. Fail attach when the controller cannot be reset or initialized, and report runtime failures through iflib_init_failed() so iflib leaves the interface stopped. Also stop register accesses and report the error when a stop path reset fails. A later successful initialization completes pending fatal error cleanup and re-arms FER. Cache a requested MAC address before reset, but let init_hw program RAR0 after reset succeeds. Let iflib perform its normal attach-post failure cleanup instead of releasing the same driver resources from both layers, and make queue cleanup idempotent. MFC after: 2 weeks Sponsored by: BBOX.io
Diffstat (limited to 'test/Transforms/LoopUnroll/runtime-loop.ll')
0 files changed, 0 insertions, 0 deletions