search for: pci_amd_iommu

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

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

-- Advanced Micro Devices GmbH Sitz: Dornach, Gemeinde Aschheim, Landkreis München Registergericht München, HRB Nr. 43632 WEEE-Reg-Nr: DE 12919551 Geschäftsführer: Alberto Bozzo, Andrew Bowd _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi all 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 on serial console: (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) Xen BUG at pci_amd_iommu.c:35 (XEN) **************************************** (XEN) (XEN) Reboot in five seconds... Error says it is a bug, but maybe there is a workaround for it. I run CentOS 6.3 and use dom0 kernel 3.7.1 and Xen from http://au1.mirror.crc.id.au/repo/el6/x86_64/ repository, but I also tried with other 3....

...h/x86/apic.c +++ b/xen/arch/x86/apic.c @@ -975,6 +975,8 @@ void __init x2apic_bsp_setup(void) goto restore_out; } + force_iommu = 1; + genapic = apic_x2apic_probe(); printk("Switched to APIC driver %s.\n", genapic->name); --- a/xen/drivers/passthrough/amd/pci_amd_iommu.c +++ b/xen/drivers/passthrough/amd/pci_amd_iommu.c @@ -164,9 +164,13 @@ int __init amd_iov_detect(void) { INIT_LIST_HEAD(&amd_iommu_head); + if ( !iommu_enable && !iommu_intremap ) + return 0; + if ( (amd_iommu_detect_acpi() !=0) || (iommu_found() == 0) ) {...

...IOMMU page tables that will never be used. The main question is what happens for MMIO ranges living above 4G. Of course, the same issue would currently exist for any such ranges sitting beyon the end of RAM. Signed-off-by: Jan Beulich <jbeulich@novell.com> --- a/xen/drivers/passthrough/amd/pci_amd_iommu.c +++ b/xen/drivers/passthrough/amd/pci_amd_iommu.c @@ -230,8 +230,16 @@ static void __init amd_iommu_dom0_init(s if ( !iommu_passthrough && !need_iommu(d) ) { /* Set up 1:1 page table for dom0 */ - for ( i = 0; i < max_page; i++ ) - amd_iommu_map_pag...

...rsion: 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 from squeeze and for 3.4-trunk and 3.5-trunk from experimental. Best Stephan PS: Furthermore note that on Linux 3.2.0.2, xen-hypervisor-4.0-amd64 floods the console/logs with powernow-k8 transition error messages, see * http://bugzilla.xen.org/bu...

...rsion: 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 from squeeze and for 3.4-trunk and 3.5-trunk from experimental. Best Stephan PS: Furthermore note that on Linux 3.2.0.2, xen-hypervisor-4.0-amd64 floods the console/logs with powernow-k8 transition error messages, see * http://bugzilla.xen.org/bu...

...;'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 on serial console: (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) Xen BUG at pci_amd_iommu.c:35 (XEN) **************************************** (XEN) (XEN) Reboot in five seconds... Is it a bug in Xen or maybe bug in BIOS? I run CentOS 6.3 and use dom0 kernel 3.7.1 and Xen from http://au1.mirror.crc.id.au/repo/el6/x86_64/ repository, but I also tried with other 3.x and 2.6.32 kernels an...

...i_os_printf io_apic_write __ioapic_write_entry ioapic_write_entry __clear_IO_APIC_pin clear_IO_APIC disable_IO_APIC __stop_this_cpu smp_send_stop machine_restart panic tasklet_schedule_on_cpu display_cacheinfo init_amd generic_identify identify_cpu _start_xen _high_start Panic on CPU 0: Xen BUG at pci_amd_iommu.c:33 ===== The patch in the next mail fixes the problem for me and the intended panic- message appears.

This patch set adds basic supports for amd next generation iommu (IOMMUv2) hardware. IOMMUv2 supports various new features advertised by iommu extended feature register. It introduces guest level IO translation and supports state-of-the-art ATS/ATC devices with demand paging capability. Please refer to AMD IOMMU Architectural Specification [1] for more details. Thanks, Wei [1]

..._irq_vector_map == OPT_IRQ_VECTOR_MAP_GLOBAL ) + if ( opt_irq_vector_map == OPT_IRQ_VECTOR_MAP_GLOBAL || + opt_irq_vector_map == OPT_IRQ_VECTOR_MAP_PERDEV_GLOBAL ) { struct irq_desc *desc = irq_to_desc(irq); diff -r 84e4d183fa8b -r 6671fc79717a xen/drivers/passthrough/amd/pci_amd_iommu.c --- a/xen/drivers/passthrough/amd/pci_amd_iommu.c +++ b/xen/drivers/passthrough/amd/pci_amd_iommu.c @@ -238,6 +238,21 @@ int __init amd_iov_detect(void) } if ( !amd_iommu_perdev_intremap ) printk(XENLOG_WARNING "AMD-Vi: Using global interrupt remap table is not recommended...