During irq migration, fixup_irqs() in arch/x86/kernel/irq.c will
call irq_force_complete_move() for every valid irqs, including
whose irq_chip is not apic(like ioapic_chip, msi_chip, etc) kind.
While the function irq_force_complete_move() in
arch/x86/kernel/apic/io_apic.c will treat all input irqs
* Jason Chen wrote:
> The function irq_force_complete_move() might handle irqs based on
> the non-apic irq_chip the way apic does, which has the structure
> irq_cfg as its chip_data.
> Wrong operations on non-apic irq_chip might make its chip_data changed
> and bring unexpected issues.
> Add api
The function irq_force_complete_move() might handle irqs based on
the non-apic irq_chip the way apic does, which has the structure
irq_cfg as its chip_data.
Wrong operations on non-apic irq_chip might make its chip_data changed
and bring unexpected issues.
Add apic_irqs bitmap to identify irqs from
3 matches
Mail list logo