RE: [PATCH] iommu/hyper-v: Fix panic on a host without the 15-bit APIC ID support

2020-12-02 Thread Dexuan Cui
> From: Thomas Gleixner > Sent: Wednesday, December 2, 2020 1:56 AM > > On Tue, Dec 01 2020 at 16:45, Dexuan Cui wrote: > > The commit f36a74b9345a itself is good, but it causes a panic in a > > Linux VM that runs on a Hyper-V host that doesn't have the 15-bit > > Extended APIC ID support: > >

Re: [PATCH] iommu/hyper-v: Fix panic on a host without the 15-bit APIC ID support

2020-12-02 Thread Thomas Gleixner
On Tue, Dec 01 2020 at 16:45, Dexuan Cui wrote: > The commit f36a74b9345a itself is good, but it causes a panic in a > Linux VM that runs on a Hyper-V host that doesn't have the 15-bit > Extended APIC ID support: > kernel BUG at arch/x86/kernel/apic/io_apic.c:2408! This has nothing to do with

Re: [PATCH] iommu/hyper-v: Fix panic on a host without the 15-bit APIC ID support

2020-12-01 Thread Woodhouse, David
On Tue, 2020-12-01 at 16:45 -0800, Dexuan Cui wrote: > The commit f36a74b9345a itself is good, but it causes a panic in a > Linux VM that runs on a Hyper-V host that doesn't have the 15-bit > Extended APIC ID support: > kernel BUG at arch/x86/kernel/apic/io_apic.c:2408! > > This happens

[PATCH] iommu/hyper-v: Fix panic on a host without the 15-bit APIC ID support

2020-12-01 Thread Dexuan Cui
The commit f36a74b9345a itself is good, but it causes a panic in a Linux VM that runs on a Hyper-V host that doesn't have the 15-bit Extended APIC ID support: kernel BUG at arch/x86/kernel/apic/io_apic.c:2408! This happens because the Hyper-V ioapic_ir_domain (which is defined in