I wonder if 2.6.17 will be the end of these firmware / SMP  
problems... I noticed this commit in the ChangeLog for kernel 2.6.17-rc1

commit 501f2499b897ca4be68b1acc7a4bc8cf66f5fd24
Author: Bryan Holty <[EMAIL PROTECTED]>
Date:   Sat Mar 25 03:07:37 2006 -0800

     [PATCH] IRQ: prevent enabling of previously disabled interrupt

     This fix prevents re-disabling and enabling of a previously  
disabled
     interrupt.  On an SMP system with irq balancing enabled; If an  
interrupt is
     disabled from within its own interrupt context with  
disable_irq_nosync and is
     also earmarked for processor migration, the interrupt is blindly  
moved to the
     other processor and enabled without regard for its current  
"enabled" state.
     If there is an interrupt pending, it will unexpectedly invoke  
the irq handler
     on the new irq owning processor (even though the irq was  
previously disabled)

     The more intuitive fix would be to invoke disable_irq_nosync and
     enable_irq, but since we already have the desc->lock from  
__do_IRQ, we
     cannot call them directly.  Instead we can use the same logic to  
disable
     and enable found in disable_irq_nosync and enable_irq, with  
regards to the
     desc->depth.

     This now prevents a disabled interrupt from being re-disabled,  
and more
     importantly prevents a disabled interrupt from being incorrectly  
enabled on
     a different processor.

     Signed-off-by: Bryan Holty <[EMAIL PROTECTED]>
     Cc: Andi Kleen <[EMAIL PROTECTED]>
     Cc: "Luck, Tony" <[EMAIL PROTECTED]>
     Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
     Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>

- Rick

On Apr 5, 2006, at 4:20 PM, Ricardo Lugo wrote:

> Wilhelm,
>
> I believe it's under Processor type and features as "Enable kernel
> irq balancing."
>
> - Rick
>
> On Apr 4, 2006, at 2:40 AM, Wilhelm Eger wrote:
>
>> Hello,
>>
>>>     1) recompile the kernel without IRQ Balancing
>>
>> I can't find such an option in my 2.6.16 menuconfig. Could you give
>> me a
>> hint?
>>
>> Regards,
>>
>> Wilhelm
>>
>> _______________________________________________
>> ivtv-devel mailing list
>> [email protected]
>> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
>
> _______________________________________________
> ivtv-devel mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel


_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Reply via email to