Mark Huth wrote:
Kok, Auke wrote:
Mark Huth wrote:
Current e1000_xmit_frame spews raw interrupt disabled nag messages when
used with RT kernel patches. This patch uses spin_trylock_irqsave,
which allows RT patches to properly manage the irq semantics.
Looks OK with me on first sight, I'll
Michal Schmidt wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kok, Auke wrote:
Mark Huth wrote:
Well, I'm not an expert on the realtime patches - but most any patch set
from Ingo seems to set this off - we've run through a bunch all the way
since 2.6.10.
that's bizarre, and would imply
Kok, Auke wrote:
uhh, sure... while we are at it then, are there any more patches like this?
perhaps for e100? ixgb?
A quick grep through the current RT patch shows there are no other
changes to e100, e1000, ixgb.
Michal
-
To unsubscribe from this list: send the line unsubscribe netdev in
Michal Schmidt wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kok, Auke wrote:
Mark Huth wrote:
Well, I'm not an expert on the realtime patches - but most any patch set
from Ingo seems to set this off - we've run through a bunch all the way
since 2.6.10.
that's
Current e1000_xmit_frame spews raw interrupt disabled nag messages when
used with RT kernel patches. This patch uses spin_trylock_irqsave,
which allows RT patches to properly manage the irq semantics.
Signed-off-by: Mark Huth [EMAIL PROTECTED]
---
diff --git a/drivers/net/e1000/e1000_main.c
Mark Huth wrote:
Current e1000_xmit_frame spews raw interrupt disabled nag messages when
used with RT kernel patches. This patch uses spin_trylock_irqsave,
which allows RT patches to properly manage the irq semantics.
Looks OK with me on first sight, I'll keep it on my stack and push it
Kok, Auke wrote:
Mark Huth wrote:
Current e1000_xmit_frame spews raw interrupt disabled nag messages when
used with RT kernel patches. This patch uses spin_trylock_irqsave,
which allows RT patches to properly manage the irq semantics.
Looks OK with me on first sight, I'll keep it on my stack
