search for: bdf

...59c..0e63e35 100644 --- a/xen/drivers/passthrough/amd/iommu_acpi.c +++ b/xen/drivers/passthrough/amd/iommu_acpi.c @@ -664,19 +664,46 @@ static void __init parse_ivrs_hpet(char *str) ASSERT(*s == ''[''); id = simple_strtoul(s + 1, &s, 0); - if ( id != (typeof(hpet_sbdf.id))id || *s != '']'' || *++s != ''='' ) + if ( (*s != '']'') || (*++s != ''='') ) return; s = parse_pci(s + 1, &seg, &bus, &dev, &func); if ( !s || *s ) return; + hpet_sbdf.id = id...

...pgd = ff25f000 (XEN) intel-iommu.c:1843: assign_device: bus = 0 dev = 2 func = 0 (XEN) intel-iommu.c:1371:d0 reassign_device-0:2:0- source = 0 target = 1 (XEN) dmar.c:110:d0 acpi_find_matched_drhd_unit: drhd->address = feb01000 (XEN) intel-iommu.c:1312:d0 domain_context_unmap:PCI: bdf = 0:2:0 (XEN) intel-iommu.c:1260:d0 domain_context_unmap_one_1:bdf = 0:2:0 (XEN) intel-iommu.c:741: iommu_page_fault: iommu->reg = fff77000 (XEN) intel-iommu.c:724: iommu_page_fault:DMA Write: DEVICE 0:2.0 addr 7e8000002 (XEN) print_vtd_entries: domain_id = 0 bdf = 0:2:0 devfn = 1...

Hello, I''ve previously been successful with Xen4 and VT-d on other systems. I am having trouble getting VT-d passthrough working to a WinXP domain with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, xm info shows hvm_directio capability, I have iommu=1 set, I have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-devices shows the devices as

Hello, I''ve previously been successful with Xen4 and VT-d on other systems. I am having trouble getting VT-d passthrough working to a WinXP domain with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, xm info shows hvm_directio capability, I have iommu=1 set, I have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-devices shows the devices as

Hello, I''m having problems with VTD on this board. The board/cpu/bios all support vt-d and I think maybe I''m just missing something? Any feedback would be much appreciated :) Output below: root@vm:~# xm create /etc/xen/vm-nine.cfg Using config file "/etc/xen/vm-nine.cfg". Error: Failed to assign device to IOMMU (0000:05:00.0@100,msitranslate=1,power_mgmt=0)

Hello, I''m having problems with VTD on this board. The board/cpu/bios all support vt-d and I think maybe I''m just missing something? Any feedback would be much appreciated :) Output below: root@vm:~# xm create /etc/xen/vm-nine.cfg Using config file "/etc/xen/vm-nine.cfg". Error: Failed to assign device to IOMMU (0000:05:00.0@100,msitranslate=1,power_mgmt=0)

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 idea...

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 idea...

...cted that the drivers 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...

...tatic u16 __init parse_ivhd_device_special( return 0; } - AMD_IOMMU_DEBUG("IVHD Special: %04x:%02x:%02x.%u variety %#x handle %#x\n", + AMD_IOMMU_DEBUG("IVHD Special: %04x:%02x:%02x.%u variety %#x handle %#x used_id %#x\n", seg, PCI_BUS(bdf), PCI_SLOT(bdf), PCI_FUNC(bdf), - special->variety, special->handle); + special->variety, special->handle, special->used_id); add_ivrs_mapping_entry(bdf, bdf, special->header.data_setting, iommu); switch ( special->variety )...

X.Org Security Advisory: March 17, 2015 More BDF file parsing issues in libXfont ======================================== Description: ============ Ilja van Sprundel, a security researcher with IOActive, has discovered an issue in the parsing of BDF font files by libXfont. Additional testing by Alan Coopersmith and William Robinet with the Am...

...g of 16 KiB. (XEN) microcode.c:73:d32767 microcode: CPU1 resumed (XEN) microcode.c:73:d32767 microcode: CPU3 resumed (XEN) Brought up 4 CPUs (XEN) microcode.c:73:d32767 microcode: CPU2 resumed (XEN) Created cpupool 0 with scheduler SMP Credit Scheduler (credit) (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:2.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:16.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:16.2 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:16.3 (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:19.0 (XEN) [VT-D]iommu.c:1332: d0:PCI: map...

...d by override. (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) ACPI: HPET id: 0x8086a301 base: 0xfed00000 (XEN) [VT-D]dmar.c:460: Host address width 36 (XEN) [VT-D]dmar.c:469: found ACPI_DMAR_DRHD (XEN) [VT-D]dmar.c:337: dmaru->address = fedae000 (XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:1b.0 (XEN) [VT-D]dmar.c:469: found ACPI_DMAR_DRHD (XEN) [VT-D]dmar.c:337: dmaru->address = fedb0000 (XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:3.0 (XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:3.2 (XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:3.3 (XEN) [VT-D]dmar.c:469: found ACPI_D...

Add commands to automatically prep devices for pass-through The current method for passing through devices requires users to either modify cryptic Linux boot parameters and reboot, or do a lot of manual reads and writes into sysfs nodes. This set of patches introduces commands to make this easier. It expands on the concept of "assignable" (from the list_assignable_devices command).

...0100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000000 libxl: error: libxl_pci.c:790:libxl__device_pci_add PCI device 0:12:0.70 is not assignable There is no function 70 on that device. In relation to that, the BDF documentation (http://wiki.xensource.com/xenwiki/BDFNotation) seems to imply that you can specify the extended BDF notation on your kernel boot line in grub. i.e. xen-pciback.hide=(0000:12:00.*) does not work. You''ll get an error in the kernel log. Actually, if you look at the code for...

...to passthrough my Intel Core gpu. But somehow it has a weird IRQ of 1251. So i cant start the vm if i set pci=[''00:02.0'']. The device is bound to the pciback driver correctly. The interesting part of xm dmesg (appears when i start the vm): (XEN) [VT-D]iommu.c:1484: d0:PCI: unmap bdf = 0:2.0 (XEN) [VT-D]iommu.c:1362: d1:PCI: map bdf = 0:2.0 (XEN) physdev.c:61: dom1: map invalid irq 1251 (XEN) [VT-D]io.c:300: d1: bind: m_gsi=55 g_gsi=36 device=5 intx=0 (XEN) [VT-D]iommu.c:1484: d1:PCI: unmap bdf = 0:2.0 (XEN) [VT-D]iommu.c:1362: d0:PCI: map bdf = 0:2.0 lspci -vvv: 00:02.0 VGA...

...to passthrough my Intel Core gpu. But somehow it has a weird IRQ of 1251. So i cant start the vm if i set pci=[''00:02.0'']. The device is bound to the pciback driver correctly. The interesting part of xm dmesg (appears when i start the vm): (XEN) [VT-D]iommu.c:1484: d0:PCI: unmap bdf = 0:2.0 (XEN) [VT-D]iommu.c:1362: d1:PCI: map bdf = 0:2.0 (XEN) physdev.c:61: dom1: map invalid irq 1251 (XEN) [VT-D]io.c:300: d1: bind: m_gsi=55 g_gsi=36 device=5 intx=0 (XEN) [VT-D]iommu.c:1484: d1:PCI: unmap bdf = 0:2.0 (XEN) [VT-D]iommu.c:1362: d0:PCI: map bdf = 0:2.0 lspci -vvv: 00:02.0 VGA...

# HG changeset patch # User George Dunlap <george.dunlap@eu.citrix.com> # Date 1337961666 0 # Node ID 1c28051020488782f1277dd60a2418324580297e # Parent 69c3ae25bb1ddcb0ea44b7566d36d34e9d6a70aa libxl: When checking BDF of existing slots, function should be decimal, not hex Spotted-by: Konrad Wilk <konrad.wilk@oracle.com> Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> diff --git a/tools/libxl/libxl_pci.c b/tools/libxl/libxl_pci.c --- a/tools/libxl/libxl_pci.c +++ b/tools/libxl/libxl_pci.c...

Hello, I''m also seeing this exact same problem. I''ve posted on xen-users, but did not get an answer. Venkat seems to be experiencing the same problem as me. I have the latest BIOS for my motherboard DQ35JO. (BIOS ver 933) I''m running a Q6600 as well. It hangs at "Brought up 4 CPUs." I''ve tried all sorts of combinations of Xen versions and kernels to

Hi, We found a bug that rombios cannot get the correct BDF during rom_scan. This patch fixes rombios to get the BDF for calling INIT function. I''m sorry for the inconvenience. m(__)m Signed-off-by: Akio Takebe <takebe_akio@jp.fujitsu.com> Signed-off-by: Kouya Shimura <kouya@jp.fujitsu.com> Best Regards, Akio Takebe _______________...