similar to: [PATCH for QEMU v2] hw/vfio: Add VMD Passthrough Quirk

Displaying 20 results from an estimated 6000 matches similar to: "[PATCH for QEMU v2] hw/vfio: Add VMD Passthrough Quirk"

2020 May 13
0
[PATCH for QEMU v2] hw/vfio: Add VMD Passthrough Quirk
On Wed, 13 May 2020 00:35:47 +0000 "Derrick, Jonathan" <jonathan.derrick at intel.com> wrote: > Hi Alex, > > I'm probably not getting the translation technical details correct. > > On Mon, 2020-05-11 at 16:59 -0600, Alex Williamson wrote: > > On Mon, 11 May 2020 15:01:27 -0400 > > Jon Derrick <jonathan.derrick at intel.com> wrote: > >
2020 May 11
0
[PATCH for QEMU v2] hw/vfio: Add VMD Passthrough Quirk
On Mon, 11 May 2020 15:01:27 -0400 Jon Derrick <jonathan.derrick at intel.com> wrote: > The VMD endpoint provides a real PCIe domain to the guest, including Please define VMD. I'm sure this is obvious to many, but I've had to do some research. The best TL;DR summary I've found is Keith's original commit 185a383ada2e adding the controller to Linux. If there's
2020 Apr 23
0
[PATCH 0/1] KVM support for VMD devices
On Wed, Apr 22, 2020 at 01:14:44PM -0400, Jon Derrick wrote: > The two patches (Linux & QEMU) add support for passthrough VMD devices > in QEMU/KVM. VMD device 28C0 already supports passthrough natively by > providing the Host Physical Address in a shadow register to the guest > for correct bridge programming. > > The QEMU patch emulates the 28C0 mode by creating a shadow
2016 Apr 18
0
[PATCH RFC 3/3] vfio: add virtio pci quirk
Modern virtio pci devices can set VIRTIO_F_IOMMU_PLATFORM to signal they are safe to use with an IOMMU. Without this bit, exposing the device to userspace is unsafe, so probe and fail VFIO initialization unless noiommu is enabled. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/vfio/pci/vfio_pci_private.h | 1 + drivers/vfio/pci/vfio_pci.c | 11 +++
2016 Aug 30
0
[PATCH v2 2/2] vfio: add virtio pci quirk
Modern virtio pci devices can set VIRTIO_F_IOMMU_PLATFORM to signal they are safe to use with an IOMMU. Without this bit, exposing the device to userspace is unsafe, so probe and fail VFIO initialization unless noiommu is enabled. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/vfio/pci/vfio_pci_private.h | 1 + drivers/vfio/pci/vfio_pci.c | 14 ++++
2016 Aug 30
0
[PATCH v2 2/2] vfio: add virtio pci quirk
On Mon, 29 Aug 2016 21:23:25 -0600 Alex Williamson <alex.williamson at redhat.com> wrote: > On Tue, 30 Aug 2016 05:27:17 +0300 > "Michael S. Tsirkin" <mst at redhat.com> wrote: > > > Modern virtio pci devices can set VIRTIO_F_IOMMU_PLATFORM > > to signal they are safe to use with an IOMMU. > > > > Without this bit, exposing the device to
2016 Aug 30
0
[PATCH v2 2/2] vfio: add virtio pci quirk
On Mon, Aug 29, 2016 at 10:53:04PM -0600, Alex Williamson wrote: > On Mon, 29 Aug 2016 21:52:20 -0600 > Alex Williamson <alex.williamson at redhat.com> wrote: > > > On Mon, 29 Aug 2016 21:23:25 -0600 > > Alex Williamson <alex.williamson at redhat.com> wrote: > > > > > On Tue, 30 Aug 2016 05:27:17 +0300 > > > "Michael S. Tsirkin"
2016 Apr 18
1
[PATCH RFC 3/3] vfio: add virtio pci quirk
On Mon, 18 Apr 2016 12:58:28 +0300 "Michael S. Tsirkin" <mst at redhat.com> wrote: > Modern virtio pci devices can set VIRTIO_F_IOMMU_PLATFORM > to signal they are safe to use with an IOMMU. > > Without this bit, exposing the device to userspace is unsafe, so probe > and fail VFIO initialization unless noiommu is enabled. > > Signed-off-by: Michael S.
2016 Apr 18
1
[PATCH RFC 3/3] vfio: add virtio pci quirk
On Mon, 18 Apr 2016 12:58:28 +0300 "Michael S. Tsirkin" <mst at redhat.com> wrote: > Modern virtio pci devices can set VIRTIO_F_IOMMU_PLATFORM > to signal they are safe to use with an IOMMU. > > Without this bit, exposing the device to userspace is unsafe, so probe > and fail VFIO initialization unless noiommu is enabled. > > Signed-off-by: Michael S.
2016 Aug 30
2
[PATCH v2 2/2] vfio: add virtio pci quirk
On Mon, 29 Aug 2016 21:52:20 -0600 Alex Williamson <alex.williamson at redhat.com> wrote: > On Mon, 29 Aug 2016 21:23:25 -0600 > Alex Williamson <alex.williamson at redhat.com> wrote: > > > On Tue, 30 Aug 2016 05:27:17 +0300 > > "Michael S. Tsirkin" <mst at redhat.com> wrote: > > > > > Modern virtio pci devices can set
2016 Aug 30
2
[PATCH v2 2/2] vfio: add virtio pci quirk
On Mon, 29 Aug 2016 21:52:20 -0600 Alex Williamson <alex.williamson at redhat.com> wrote: > On Mon, 29 Aug 2016 21:23:25 -0600 > Alex Williamson <alex.williamson at redhat.com> wrote: > > > On Tue, 30 Aug 2016 05:27:17 +0300 > > "Michael S. Tsirkin" <mst at redhat.com> wrote: > > > > > Modern virtio pci devices can set
2016 Dec 13
1
virsh not detecting hugepage mount; disabled by config?
Hi, I’m struggling with virsh not detecting my hugepage mount. I have the following kernel command line: BOOT_IMAGE=/vmlinuz-4.8.13-gentoo root=/dev/mapper/gensd-gentoo ro quiet splash intel_iommu=on video=efifb:off,vesafb:off,simplefb:off splash=verbose,theme:livedvd-aurora kvm.ignore_msrs=1 transparent_hugepage=never hugepages=3072 softlevel=qemuvm My startup script outputs the following:
2016 Dec 14
0
Re: virsh not detecting hugepage mount; disabled by config?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Thanks a lot you two, yes hugetlbfs is not mounted, when libvirtd is started… It was a long night. Did put it to fstab and since I do not allocate them on regular boots, it won’t eat my ram (that was the main consideration for doing it like this). As a last means before going to sleep, I added <qemu:arg value='-numa'/>
2016 Aug 30
4
[PATCH v2 2/2] vfio: add virtio pci quirk
On Tue, 30 Aug 2016 05:27:17 +0300 "Michael S. Tsirkin" <mst at redhat.com> wrote: > Modern virtio pci devices can set VIRTIO_F_IOMMU_PLATFORM > to signal they are safe to use with an IOMMU. > > Without this bit, exposing the device to userspace is unsafe, so probe > and fail VFIO initialization unless noiommu is enabled. > > Signed-off-by: Michael S.
2016 Aug 30
4
[PATCH v2 2/2] vfio: add virtio pci quirk
On Tue, 30 Aug 2016 05:27:17 +0300 "Michael S. Tsirkin" <mst at redhat.com> wrote: > Modern virtio pci devices can set VIRTIO_F_IOMMU_PLATFORM > to signal they are safe to use with an IOMMU. > > Without this bit, exposing the device to userspace is unsafe, so probe > and fail VFIO initialization unless noiommu is enabled. > > Signed-off-by: Michael S.
2010 Jul 01
0
[XCP] updates.vmd.citrix.com
Good day. xe-guest-tools for debian adding a repository to aptitude:/etc/apt/sources.list.d/citrix.list deb http://updates.vmd.citrix.com/XCP/0.4.901/debian/ lenny main deb-src http://updates.vmd.citrix.com/XCP/0.4.901/debian/ lenny main But this repository does not work: Err http://updates.vmd.citrix.com lenny/main Packages 404 Not Found Err http://updates.vmd.citrix.com lenny/main
2018 Jan 22
2
[Bug 104728] New: [possible regression] VMD crashes on startup on GT 640 / GK107 / NVE7
https://bugs.freedesktop.org/show_bug.cgi?id=104728 Bug ID: 104728 Summary: [possible regression] VMD crashes on startup on GT 640 / GK107 / NVE7 Product: Mesa Version: 17.2 Hardware: All OS: All Status: NEW Severity: major Priority: medium Component:
2020 Apr 14
0
[RFC PATCH 11/34] iommu: Split off default domain allocation from group assignment
Hi Jonathan, On Mon, Apr 13, 2020 at 10:10:50PM +0000, Derrick, Jonathan wrote: > I had to add the following for initial VMD support. The new PCIe domain > added on VMD endpoint probe didn't have the dev_iommu member set on the > VMD subdevices, which I'm guessing is due to probe_iommu_group already > having been run on the VMD endpoint's group prior to those subdevices
2012 Oct 15
1
[QEMU PATCH v4] create struct for machine initialization arguments
This should help us to: - More easily add or remove machine initialization arguments without having to change every single machine init function; - More easily make mechanical changes involving the machine init functions in the future; - Let machine initialization forward the init arguments to other functions more easily. This change was half-mechanical process: first the struct was added
2020 Jul 15
0
[PATCH 0/7] *** IRQ offloading for vDPA ***
On 2020/7/12 ??10:52, Zhu Lingshan wrote: > Hi All, > > This series intends to implement IRQ offloading for > vhost_vdpa. > > By the feat of irq forwarding facilities like posted > interrupt on X86, irq bypass can help deliver > interrupts to vCPU directly. > > vDPA devices have dedicated hardware backends like VFIO > pass-throughed devices. So it would be