Andi Kleen wrote:
quoted text
> Tejun Heo <htejun@gmail.com> writes:
>> Let's assume there's a device which shares its INTX IRQ line with
>> another device and the other one is already initialized.  During boot,
>> due to BIOS's fault, bad hardware design or sheer bad luck, the device
>> has got a pending IRQ.
> 
> This seems to be also common after kexec during kexec crashdumps
> where the device just continues doing what it did before the crash.
> 
>> This patch expands the pci_set_master() approach.  Instead of enabling
>> the device in one go, it's done in two steps - prepare and activate.
>> 'prepare' enables access to PCI configuration,
> 
> I hope there aren't any new erratas triggered by this. Perhaps it would
> make sense to add some paranoia sleeps at least before touching other
> state? 

Do you mean between disabling IRQ mechanisms and enabling PCI device in 
pcim_prepare_device()?

Thanks.

-- 
tejun
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/