similar to: Questions about direct hardware access, DMA, etc

I know most of the motherboards based off of the Intel Q35 northbridge usually have VT-d options for it to be enabled or disabled in the BIOS.  I''ve heard the same for Intel 5400''s and Intel 3200/3210''s but been looking through manuals for various server boards and don''t see VT-d options in the BIOS. However, I was wondering if anyone had success stories or

Hi, All the reviews for the AMD 890fx chipset reported that it supports IOMMU v1.2. But I cannot find any mention of that on AMD site. Does 890fx support IOMMU? Do 890fx motherboards with IOMMU exist? Does Xen support 890fx? Regards, Leonardo _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hey everyone, I realize that people asking about PCI passthrough has been thoroughly beaten to death many a time, however I couldn''t find the answer to these questions anywhere (and I''d really like to know :P) so please just bare with me. I know the GART built into AMD chipsets can act as a "mini IOMMU" and do DMA translation but not protection/isolation. However,

Folks, I download the Neocleus 1:1 patch from following link: http://lists.xensource.com/archives/html/xen-devel/2007-05/msg01144.html Currently I want to add Neocleus 1:1 Patch to the xen-3.1.0 to make the HVM guest grab the device directly. When I add these patches and recompile and install the Xen source and try to start the HVM guest, the HVM guest can not start and the system hang.

int.patch: - Supports only level-triggered interrupts. Edge interrupts support will be added shortly (should be fairly simple) - Change polarity trick: in order to reflect the external device''s assertion state, the ioapic pin gets its polarity changed whenever an interrupt occur. So an interrupt is generated when the _external_ line is asserted (then,

Hi Ian, There have been a lot of interest on gfx passthru recently. This patch enables ATI VBIOS in passthru mode. The guest VM system BIOS (including Windows boot logo) can now show in passthru screen. We have tested with various Windows and Linux guest VMs. Please help review it. We are also looking forward to comments and suggestions from Xen community users. Signed-off-by: Wei Huang

Hi all, I would like to get my system to work with IOMMU. (The long-term goal is VGA passthru.) System is as follows: CPU: Core 2 Duo E6600 MB: Foxconn G9657MA-8EKRS2H (w. latest bios: 631F1P61) Virtualization support is enabled in BIOS. (These is only one option.) Hypervisor: xen 4.0.0 from Debian, AMD64 Xen config: iommu=verbose output of xen dmesg is attached. HVM domains work (lasd tried

Convert the AMD iommu driver to the dma-iommu api. Remove the iova handling and reserve region code from the AMD iommu driver. Change-log: V4: -Rebase on top of linux-next -Split the removing of the unnecessary locking in the amd iommu driver into a seperate patch -refactor the "iommu/dma-iommu: Handle deferred devices" patch and address comments v3: -rename dma_limit to dma_mask -exit

Convert the AMD iommu driver to the dma-iommu api. Remove the iova handling and reserve region code from the AMD iommu driver. Change-log: V4: -Rebase on top of linux-next -Split the removing of the unnecessary locking in the amd iommu driver into a seperate patch -refactor the "iommu/dma-iommu: Handle deferred devices" patch and address comments v3: -rename dma_limit to dma_mask -exit

Convert the AMD iommu driver to the dma-iommu api. Remove the iova handling and reserve region code from the AMD iommu driver. Change-log: V6: -add more details to the description of patch 001-iommu-amd-Remove-unnecessary-locking-from-AMD-iommu-.patch -rename handle_deferred_device to iommu_dma_deferred_attach -fix double tabs in 0003-iommu-dma-iommu-Handle-deferred-devices.patch V5: -Rebase on

Hi, The following 4 patches enable direct device assignment (PCI passthru) for HVM guest on AMD IOMMU platforms. Please apply them against C/S 16491 as the named order. To enable AMD IOMMU, please add "enable_amd_iommu" as xen boot parameter. 1-cleanup.patch: code cleanup, bug fix, minor enhancements to existing amd-iommu codes. 2-passthru-amd.patch: passthru support, modifications to

Hi all, I were upgrading my system recently. But I met some difficult problems, the biggest one is described in http://permalink.gmane.org/gmane.comp.emulators.xen.user/66971, unfortunately I got no answer yet. My original environment is xen3.4.2(64bit) + dom0 kernel 2.6.18-xen, and 4 domus with kernel 2.6.18-xen, after first upgrade stage, I have Xen4.1.0(64bit)+dom0 kernel 2.6.32.39, and 4 domu

Hi all, I were upgrading my system recently. But I met some difficult problems, the biggest one is described in http://permalink.gmane.org/gmane.comp.emulators.xen.user/66971, unfortunately I got no answer yet. My original environment is xen3.4.2(64bit) + dom0 kernel 2.6.18-xen, and 4 domus with kernel 2.6.18-xen, after first upgrade stage, I have Xen4.1.0(64bit)+dom0 kernel 2.6.32.39, and 4 domu

On Xen-3.3.0, domain0 Megaraid SAS (SAS 1068 controller) driver is not loading correctly if vtd support in Xen is enabled. It fails at the point of initializing firmware. I wasn''t seeing this error with Xen-3.2.2-rc3 (Unstable version), though with vtd disabled in Xen-3.3.0, it is working. Looks like a degrade problem. Any clues? Thx, Venkat

hi, i have installed Xen hypervisor on fedora 17 and now i want to assign devices directly to a guest OS through VT-d. does any one know how can i do it? i found some solutions for that but those had some steps for when installing Xen while i installed Xen on fedora. i am going to know,can i assign device to a guest OS through VT-d capability with installed Xen on fedora 17? thanks.

hi, i have installed Xen hypervisor on fedora 17 and now i want to assign devices directly to a guest OS through VT-d. does any one know how can i do it? i found some solutions for that but those had some steps for when installing Xen while i installed Xen on fedora. i am going to know,can i assign device to a guest OS through VT-d capability with installed Xen on fedora 17? thanks.

Add a flush_iotlb_range to allow flushing of an iova range instead of a full flush in the dma-iommu path. Allow the iommu_unmap_fast to return newly freed page table pages and pass the freelist to queue_iova in the dma-iommu ops path. This patch is useful for iommu drivers (in this case the intel iommu driver) which need to wait for the ioTLB to be flushed before newly free/unmapped page table

Add a flush_iotlb_range to allow flushing of an iova range instead of a full flush in the dma-iommu path. Allow the iommu_unmap_fast to return newly freed page table pages and pass the freelist to queue_iova in the dma-iommu ops path. This patch is useful for iommu drivers (in this case the intel iommu driver) which need to wait for the ioTLB to be flushed before newly free/unmapped page table

Hi Folks, I make I new approach to pimp up my xen-Kernel in higher version-numbers. Currently I run a selfcompiled 2.6.27-Kernel from: hg clone http://xenbits.xensource.com/ext/linux-2.6.27-xen.hg In the next step I want to run the kernel from jemery: git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git I tried the last couple of days to get pci-passtrough work with jeremys

https://bugs.freedesktop.org/show_bug.cgi?id=58776 Priority: medium Bug ID: 58776 Assignee: nouveau at lists.freedesktop.org Summary: DRM NOUVEAU: cannot boot with kernel >=3.7 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: balducci at