similar to: [PATCH] qemu-xen: Intel GPU passthrough, fix OpRegion mapping.

Displaying 20 results from an estimated 100 matches similar to: "[PATCH] qemu-xen: Intel GPU passthrough, fix OpRegion mapping."

2012 Dec 20
25
[PATCH] hvmloader / qemu-xen: Getting rid of resource conflict for OpRegion.
This is hvmloader part of the change that gets rid of the resource conflict warning in the guest kernel. The OpRegion may not always be page aligned. As a result one extra page is required to fully accommodate the OpRegion in that case. Just reserve one more page here. Signed-off-by: Timothy Guo <firemeteor@users.sourceforge.net> diff -r 11b4bc743b1f tools/firmware/hvmloader/e820.c ---
2008 Jun 27
2
PCI device assignment to guests (userspace)
Userspace patches for the pci-passthrough functionality. The major updates since the last post are: - Loop to add passthrough devices in pc_init1 - Handle errors in read/write calls - Allow invocation without irq number for in-kernel irqchip Other than this, several small things were fixed according to review comments received last time.
2008 Jun 27
2
PCI device assignment to guests (userspace)
Userspace patches for the pci-passthrough functionality. The major updates since the last post are: - Loop to add passthrough devices in pc_init1 - Handle errors in read/write calls - Allow invocation without irq number for in-kernel irqchip Other than this, several small things were fixed according to review comments received last time.
2013 Nov 02
2
"pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x1:0x0.0x0". in qemu-dm-example.hvm.log
hi, I want to pass through "01:00.0",declared as pci=['01:00.0'] in cfg file. but found error log "pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x1:0x0.0x0". in qemu-dm-example.hvm.log In fact, /dev/xen/pci_iomul does not exist. So where /dev/xen/pci_iomul implemented ? I have searched xen and linux code,
2013 Feb 07
41
Patch series for IGD passthrough
This series contains all the fixes required to produce a working IGD passthrough box. All the changes are previously seen in the dev list but not yet accepted. Some of them are out-dated and need some reshape. Detailed description can be found later in each patch. . [PATCH 1/3] qemu-xen-trad/pt_msi_disable: do not clear all MSI flags . [PATCH 2/3] qemu-xen-trad: Correctly expose PCH ISA bridge
2020 Apr 28
5
[PATCH 0/1] Add uvirtio for testing
This is a way to create virtio based devices from user space. This is the background for this patch: We have some images works fine under qemu, we'd like to also run the same image on Google Cloud. Currently Google Cloud doesn't support virtio-vga. I had a patch to create a virtio-vga from kernel directly: https://www.spinics.net/lists/dri-devel/msg248573.html Then I got feedback from
2020 Apr 28
5
[PATCH 0/1] Add uvirtio for testing
This is a way to create virtio based devices from user space. This is the background for this patch: We have some images works fine under qemu, we'd like to also run the same image on Google Cloud. Currently Google Cloud doesn't support virtio-vga. I had a patch to create a virtio-vga from kernel directly: https://www.spinics.net/lists/dri-devel/msg248573.html Then I got feedback from
2020 Apr 30
2
[PATCH 0/1] Add uvirtio for testing
On Wed, Apr 29, 2020 at 08:59:18PM -0700, lepton wrote: > On Wed, Apr 29, 2020 at 4:58 AM Gerd Hoffmann <kraxel at redhat.com> wrote: > > > > > 3) Need to be verbose on how the vring processing work in the commit log of > > > patch 1 > > > > Ecven better a file documenting the interface somewhere in > > Documentation/ > I put a uvirtio-vga.c
2012 Jun 24
2
pt_pci_read_config offset issue
Using Xen 4.2 unstable rev. 25483. I get errors like this: pt_pci_read_config: [00:10:0] Error: Failed to read register with offset exceeding FFh. [Offset:ffh][Length:1] in my qemu log for a domU with some devices passed through to it. I investigated and found that at hw/pass-through.c line 1717
2012 Dec 03
21
Issue about domU missing interrupt
Hi developers, I met some domU issues and the log suggests missing interrupt. Details from here: http://www.gossamer-threads.com/lists/xen/users/263938#263938 In summary, this is the suspicious log: (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3 I''ve checked the code in question and found that mode 3 is an ''reserved_1'' mode. I want to trace down the source of this
2010 May 10
5
GFX Passthrough
Hi List, many People seem to be interested in the Graphic-Card Passthrough Feature (for more or less obvious reasons). Official Support is still under development, and i hope not to interfere with it in any (bad) way ... But i remember my own painfull and timeconsuming research when i wanted this feature to work, so i thought perhaps this spares some time for the unpatient users like me :)
2012 Nov 13
6
Does xen-4.2.0 support VGA passthrough with the virtual machine created by xl command?
Hi, everyone! I am working on xen-4.2.0 with spice remote connect. My host is Fedora 14 and guest is win7. I have installed spice package and now I can connect to guest by spice client. For better graphics experience, I want to try the VGA passthrough. With spice tool, I have to create a VM by xl command, and now I am wondering if it supports VGA passghrouth? If so, how should I test it ?
2009 May 20
0
[PATCHv2-RFC 2/2] qemu-kvm: use common code for assigned msix
For assigned devices, use common code to enable msi-x. We need a special "assigned" option as assigned devices lack a standard way to get vector usage. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- hw/device-assignment.c | 329 ++++++++++++------------------------------------ hw/device-assignment.h | 7 +- hw/msix.c | 9 ++- hw/pci.h
2009 May 20
0
[PATCHv2-RFC 2/2] qemu-kvm: use common code for assigned msix
For assigned devices, use common code to enable msi-x. We need a special "assigned" option as assigned devices lack a standard way to get vector usage. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- hw/device-assignment.c | 329 ++++++++++++------------------------------------ hw/device-assignment.h | 7 +- hw/msix.c | 9 ++- hw/pci.h
2009 May 11
0
[PATCH 2/2] qemu-kvm: use common code for assigned msix
For assigned devices, use common code to enable msi-x. Add "hack" option as assigned devices lack a standard way to get vector usage. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- hw/device-assignment.c | 336 ++++++++++++------------------------------------ hw/device-assignment.h | 8 +- hw/msix.c | 11 ++- hw/pci.h | 4 + 4 files
2009 May 11
0
[PATCH 2/2] qemu-kvm: use common code for assigned msix
For assigned devices, use common code to enable msi-x. Add "hack" option as assigned devices lack a standard way to get vector usage. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- hw/device-assignment.c | 336 ++++++++++++------------------------------------ hw/device-assignment.h | 8 +- hw/msix.c | 11 ++- hw/pci.h | 4 + 4 files
2009 Jul 14
0
[patch]: qemu-xen: pass-through: pt_reset_interrupt_and_io_mapping(): use hw INTX
This fixes a few things that I missed in previous patches: * Use the hw INTX rather than INTA in pt_reset_interrupt_and_io_mapping() This is consistent with other uses of pci_intx() * Remove now inaccurate "/* fix virtual interrupt pin to INTA# */" comments * Use PCI_SLOT() Signed-off-by: Simon Horman <horms@verge.net.au> Index: ioemu-remote/hw/pass-through.c
2013 Jul 24
4
[PATCH 2/3] V5 qemu-xen-trad: Correctly expose PCH ISA bridge for IGD passthrough
The i915 driver probes chip version through PCH ISA bridge device / vendor ID. Previously, the PCH ISA bridge is exposed as PCI-PCI bridge in qemu-xen-trad, which breaks the assumption of the driver. This change fixes the issue by correctly exposing the ISA bridge to domU. Signed-off-by: Rui Guo <firemeteor@users.sourceforge.net> Tested-by: Rui Guo <firemeteor@users.sourceforge.net>
2008 Sep 17
7
Megaraid SAS driver failing in Xen-3.3.0 but was working in Xen-3.2.2-rc3
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
2011 May 18
90
Patches for VGA-Passthrough XEN 4.2 unstable
Hello, I have been working on VGA-passthrough in the last month. When Xen was at his version 3.5 there was a few patches to make this work for some graphic cards using the patches developed by Han Weidong and posted here (http://lists.xensource.com/archives/html/xen-devel/2009-08/msg01176.html) and the same patches posted file by file are here