> From: David Woodhouse
> Sent: Tuesday, November 3, 2020 12:03 AM
> > +/*
> > + * If ms_hyperv_msi_ext_dest_id() returns true,
> > hyperv_prepare_irq_remapping()
> > + * returns -ENODEV and the Hyper-V IOMMU driver is not used; instead, the
> > + * generic support of the 15-bit APIC ID is used: s
> From: Dexuan Cui
> Sent: Monday, November 2, 2020 5:12 PM
>
> ...
Hi tglx,
Now this patch is in the x86/apic branch, which is great! Thanks for the
quick action! But the third line of the below paragraph of the commit log
is missing... Sorry I just realized I should have not prefixed that lin
On Mon, 2020-11-02 at 17:11 -0800, Dexuan Cui wrote:
> When a Linux VM runs on Hyper-V, if the VM has CPUs with >255 APIC IDs,
> the CPUs can't be the destination of IOAPIC interrupts, because the
> IOAPIC RTE's Dest Field has only 8 bits. Currently the hackery driver
> drivers/iommu/hyperv-iommu.c
Hi Dexuan,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/x86/core]
[also build test ERROR on tip/master v5.10-rc2 next-20201102]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as docu
> From: Dexuan Cui
> Sent: Monday, November 2, 2020 5:12 PM
Sorry I forgot to mention that this patch is based on tip.git's x86/apic branch.
Thanks,
-- Dexuan
When a Linux VM runs on Hyper-V, if the VM has CPUs with >255 APIC IDs,
the CPUs can't be the destination of IOAPIC interrupts, because the
IOAPIC RTE's Dest Field has only 8 bits. Currently the hackery driver
drivers/iommu/hyperv-iommu.c is used to ensure IOAPIC interrupts are
only routed to CPUs
6 matches
Mail list logo