* Eric W. Biederman <[email protected]> wrote: > Ingo would it be reasonable to get a wait queue so I can wait for an > irq that needs the delayed disable action to actually become masked? that might make sense, but what will do the wakeup - incidental IRQ arriving on the new CPU? Isnt that a bit risky - maybe the device wont generate IRQs for a really long time. Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH 2/2] x86_64 irq: Handle irqs pending in IRR during irq migration.
- From: [email protected] (Eric W. Biederman)
- Re: [PATCH 2/2] x86_64 irq: Handle irqs pending in IRR during irq migration.
- From: [email protected] (Eric W. Biederman)
- Re: [PATCH 2/2] x86_64 irq: Handle irqs pending in IRR during irq migration.
- References:
- Re: System crash after "No irq handler for vector" linux 2.6.19
- From: [email protected] (Eric W. Biederman)
- [PATCH 1/2] x86_64 irq: Simplfy __assign_irq_vector
- From: [email protected] (Eric W. Biederman)
- [PATCH 2/2] x86_64 irq: Handle irqs pending in IRR during irq migration.
- From: [email protected] (Eric W. Biederman)
- Re: [PATCH 2/2] x86_64 irq: Handle irqs pending in IRR during irq migration.
- From: Ingo Molnar <[email protected]>
- Re: [PATCH 2/2] x86_64 irq: Handle irqs pending in IRR during irq migration.
- From: [email protected] (Eric W. Biederman)
- Re: System crash after "No irq handler for vector" linux 2.6.19
- Prev by Date: Re: [patch] x86-64 ext2/ext3 datestamp problem
- Next by Date: Re: [2.6 patch] remove the broken FB_S3TRIO driver
- Previous by thread: Re: [PATCH 2/2] x86_64 irq: Handle irqs pending in IRR during irq migration.
- Next by thread: Re: [PATCH 2/2] x86_64 irq: Handle irqs pending in IRR during irq migration.
- Index(es):
 |