es appear in a DRHD's
device scope.
Enhance the document by mentioning what could happen when bypass_iommu
is used under Linux guest.
For detailed qemu cmdline and guest kernel dmesg, please see:
https://lore.kernel.org/qemu-devel/20240510072519.GA39314@ziqianlu-desk2/
Reported-by: Juro Bystrick
On Thu, May 23, 2024 at 08:52:35PM +0800, Aaron Lu wrote:
> On Wed, May 22, 2024 at 08:34:13PM +0800, Aaron Lu wrote:
> >
> > I do not have Windows VM right now and will report back once I finished
> > testing there.
>
> Tested with a Windows 10 VM and turnes out virt
On Wed, May 22, 2024 at 08:34:13PM +0800, Aaron Lu wrote:
>
> I do not have Windows VM right now and will report back once I finished
> testing there.
Tested with a Windows 10 VM and turnes out virtio pci devices always
use MSI no matter vIOMMU and bypass iommu are specified or
On Wed, May 22, 2024 at 05:28:50AM -0400, Michael S. Tsirkin wrote:
> On Wed, May 22, 2024 at 03:40:08PM +0800, Aaron Lu wrote:
> > When Intel vIOMMU is used and irq remapping is enabled, using
> > bypass_iommu will cause following two callstacks dumped during kernel
> > boo
7;s
device scope.
Enhance the document by mentioning what could happen when bypass_iommu
is used.
For detailed qemu cmdline and guest kernel dmesg, please see:
https://lore.kernel.org/qemu-devel/20240510072519.GA39314@ziqianlu-desk2/
Reported-by: Juro Bystricky
Signed-off-by: Aaron Lu
---
Hi,
When bypass iommu is used together with split irqchip, during boot,
kernel would dump 2 callstacks(see attached) and the results are pci
devices attached to root bus will fall back to using IOAPIC instead of
MSIx. This problem was initally noticed by Juro.
This only happens with kernel-irqchi
