[ipxe-devel] Negative implications of doing undinet_poll loop even if ISR not triggered?

Jarrod Johnson jarrod.b.johnson at gmail.com
Sat Feb 4 15:24:13 UTC 2012

So I'm faced with a few situations where a device makes it appear that it
supports interrupts, but undinet_isr_trigered behavior suggests that it
really doesn't.  As noted in one of the commit log messages, this does not
work at all.

If I leave everything alone, but remove the return if isr not triggered,
everything *seems* fine on these systems and existing systems don't seem
broken by it.

What bad behavior is feared if undinet_poll proceeds through on a proper
stack with interrupts working but no interrupt triggered at the time?  Is
it just an efficiency thing or are there scenarios that somehow get broken
by this sort of strategy?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20120204/79a70e2c/attachment.htm>

More information about the ipxe-devel mailing list