search for: ivrs_bdf_entri

Hi Wei, A Debian user has hit this message and reported it in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684661 I think it is the BUG_ON in: struct amd_iommu *find_iommu_for_device(int bdf) { BUG_ON ( bdf >= ivrs_bdf_entries ); return ivrs_mappings[bdf].iommu; } It looks like ivrs_bdf_entries comes from ACPI. Unfortunately the bug report is a bit vague about things like stack traces etc so it's hard to say where BDF came from. Any ideas? I'll also follow up to the submitter to try and ge...

Hi Wei, A Debian user has hit this message and reported it in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684661 I think it is the BUG_ON in: struct amd_iommu *find_iommu_for_device(int bdf) { BUG_ON ( bdf >= ivrs_bdf_entries ); return ivrs_mappings[bdf].iommu; } It looks like ivrs_bdf_entries comes from ACPI. Unfortunately the bug report is a bit vague about things like stack traces etc so it's hard to say where BDF came from. Any ideas? I'll also follow up to the submitter to try and ge...

Package: xen-hypervisor-4.1-amd64 Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-5 Severity: important I updated from xen-hypervisor-4.0-amd64 to xen-hypervisor-4.1-amd64 and the system did not boot anymore (Xen panic). A downgrade made the system work again. I cannot paste the boot error messages but the main message was: Xen BUG at pci_amd_iommu.c:33 The bug appears for Linux images 3.2.0.2

Package: xen-hypervisor-4.1-amd64 Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-5 Severity: important I updated from xen-hypervisor-4.0-amd64 to xen-hypervisor-4.1-amd64 and the system did not boot anymore (Xen panic). A downgrade made the system work again. I cannot paste the boot error messages but the main message was: Xen BUG at pci_amd_iommu.c:33 The bug appears for Linux images 3.2.0.2

Hello everyone, Reposting with after having applied the (minor) fixes suggested by Wei and Jan. Allen, if you can tell us what you think about this, or suggest someone else to ask some feedback to, if you''re no longer involved with VT-d, that would be great! :-) -- As already discussed here [1], dealing with IOMMU faults in interrupt context may cause nasty things to happen, up to

...ers there are going to try to take care of the problem. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/drivers/passthrough/amd/iommu_init.c +++ b/xen/drivers/passthrough/amd/iommu_init.c @@ -625,6 +625,18 @@ static void parse_event_log_entry(struct for ( bdf = 0; bdf < ivrs_bdf_entries; bdf++ ) if ( get_dma_requestor_id(iommu->seg, bdf) == device_id ) { + const struct pci_dev *pdev; + + spin_lock(&pcidevs_lock); + pdev = pci_get_pdev(iommu->seg, PCI_BUS(bdf), PCI_DEVFN2(bdf)); + if (...

Hi all I already posted about this problem on xen-users some time ago (http://markmail.org/message/sbgtyjqh6bzmqx4s) but I couldn''t resolve my problem using help from people on xen-users, so I''m posting here . I have a problem with enabling IOMMU on Xen 4.2.1. When I enable it in BIOS and in grub.conf using iommu=1 kernel option, my machine cannot boot. I get a following error

1: IOMMU: properly check whether interrupt remapping is enabled 2: AMD IOMMU: only disable when certain IVRS consistency checks fail 3: VT-d: deal with 5500/5520/X58 errata Patch 1 and 2 are version 2 of a previously submitted, then withdrawn patch following up after XSA-36. Patch 3 is version 3 of a patch previously sent by Malcolm and Andrew. Signed-off-by: Jan Beulich