Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

On Fri, Apr 27, 2018 at 12:15:01AM +0530, Kirti Wankhede wrote: > > > On 4/26/2018 1:22 AM, Dr. David Alan Gilbert wrote: > > * Alex Williamson (alex.william...@redhat.com) wrote: > >> On Wed, 25 Apr 2018 21:00:39 +0530 > >> Kirti Wankhede wrote: > >> > >>> On 4/25/2018 4:29

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

On Thu, 26 Apr 2018 19:55:23 +0100 "Dr. David Alan Gilbert" wrote: > * Kirti Wankhede (kwankh...@nvidia.com) wrote: > > > > > > On 4/26/2018 1:22 AM, Dr. David Alan Gilbert wrote: > > > * Alex Williamson (alex.william...@redhat.com) wrote: > > >> On Wed, 25 Apr 2018

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

* Kirti Wankhede (kwankh...@nvidia.com) wrote: > > > On 4/26/2018 1:22 AM, Dr. David Alan Gilbert wrote: > > * Alex Williamson (alex.william...@redhat.com) wrote: > >> On Wed, 25 Apr 2018 21:00:39 +0530 > >> Kirti Wankhede wrote: > >> > >>> On 4/25/2018 4:29 AM, Alex

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

On 4/26/2018 1:22 AM, Dr. David Alan Gilbert wrote: > * Alex Williamson (alex.william...@redhat.com) wrote: >> On Wed, 25 Apr 2018 21:00:39 +0530 >> Kirti Wankhede wrote: >> >>> On 4/25/2018 4:29 AM, Alex Williamson wrote: On Wed, 25 Apr 2018 01:20:08 +0530 Kirti

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

On Thu, 26 Apr 2018 08:14:27 +0200 Gerd Hoffmann wrote: > On Thu, Apr 26, 2018 at 03:44:15AM +, Tian, Kevin wrote: > > > From: Alex Williamson > > > Sent: Thursday, April 19, 2018 2:32 AM > > > > > > That almost begins to look reasonable, but then we can only expose this

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

On Thu, Apr 26, 2018 at 03:44:15AM +, Tian, Kevin wrote: > > From: Alex Williamson > > Sent: Thursday, April 19, 2018 2:32 AM > > > > That almost begins to look reasonable, but then we can only expose this > > for mdev devices, what if we were to hack a back door into a directly > > assigned

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

> From: Alex Williamson > Sent: Thursday, April 19, 2018 2:32 AM > > That almost begins to look reasonable, but then we can only expose this > for mdev devices, what if we were to hack a back door into a directly > assigned GPU that tracks the location of active display in the > framebuffer and

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

* Alex Williamson (alex.william...@redhat.com) wrote: > On Wed, 25 Apr 2018 21:00:39 +0530 > Kirti Wankhede wrote: > > > On 4/25/2018 4:29 AM, Alex Williamson wrote: > > > On Wed, 25 Apr 2018 01:20:08 +0530 > > > Kirti Wankhede wrote: > > > > > >>

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

On Wed, 25 Apr 2018 21:00:39 +0530 Kirti Wankhede wrote: > On 4/25/2018 4:29 AM, Alex Williamson wrote: > > On Wed, 25 Apr 2018 01:20:08 +0530 > > Kirti Wankhede wrote: > > > >> On 4/24/2018 3:10 AM, Alex Williamson wrote: > >>> On Wed, 18 Apr

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

On 4/25/2018 4:29 AM, Alex Williamson wrote: > On Wed, 25 Apr 2018 01:20:08 +0530 > Kirti Wankhede wrote: > >> On 4/24/2018 3:10 AM, Alex Williamson wrote: >>> On Wed, 18 Apr 2018 12:31:53 -0600 >>> Alex Williamson wrote: >>> On Mon,

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

> -Original Message- > From: intel-gvt-dev [mailto:intel-gvt-dev-boun...@lists.freedesktop.org] On > Behalf Of Alex Williamson > Sent: Wednesday, April 25, 2018 1:36 AM > To: Gerd Hoffmann > Cc: k...@vger.kernel.org; Erik Skultety ; libvirt >

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

On Wed, 25 Apr 2018 01:20:08 +0530 Kirti Wankhede wrote: > On 4/24/2018 3:10 AM, Alex Williamson wrote: > > On Wed, 18 Apr 2018 12:31:53 -0600 > > Alex Williamson wrote: > > > >> On Mon, 9 Apr 2018 12:35:10 +0200 > >> Gerd Hoffmann

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

On 4/24/2018 3:10 AM, Alex Williamson wrote: > On Wed, 18 Apr 2018 12:31:53 -0600 > Alex Williamson wrote: > >> On Mon, 9 Apr 2018 12:35:10 +0200 >> Gerd Hoffmann wrote: >> >>> This little series adds three drivers, for demo-ing and testing vfio

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

On Tue, 24 Apr 2018 09:17:37 +0200 Gerd Hoffmann wrote: > Hi, > > > Here's another proposal that's really growing on me: > > > > * Fix the vendor drivers! Allow devices to be opened and probed > >without these external dependencies. > > Hmm. If you try use gvt

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

Hi, > Here's another proposal that's really growing on me: > > * Fix the vendor drivers! Allow devices to be opened and probed >without these external dependencies. Hmm. If you try use gvt with tcg then, wouldn't qemu think "device probed ok, all green" then even though that isn't the

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

On Wed, 18 Apr 2018 12:31:53 -0600 Alex Williamson wrote: > On Mon, 9 Apr 2018 12:35:10 +0200 > Gerd Hoffmann wrote: > > > This little series adds three drivers, for demo-ing and testing vfio > > display interface code. There is one mdev device

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

On 19/04/2018 10:40, Gerd Hoffmann wrote: >> So I was ready to return and suggest that maybe libvirt should probe >> the device to know about these ancillary configuration details, but >> then I remembered that both mdev vGPU vendors had external dependencies >> to even allow probing the device.

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

On Thu, 19 Apr 2018 10:40:18 +0200 Gerd Hoffmann wrote: > > So I was ready to return and suggest that maybe libvirt should probe > > the device to know about these ancillary configuration details, but > > then I remembered that both mdev vGPU vendors had external dependencies >

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

On 2018.04.19 10:40:18 +0200, Gerd Hoffmann wrote: > Hi, > > > Erik Skultety brought up a good question today regarding how libvirt is > > meant to handle these different flavors of display interfaces and > > knowing whether a given mdev device has display support at all. It > > seems that we

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

Hi, > Erik Skultety brought up a good question today regarding how libvirt is > meant to handle these different flavors of display interfaces and > knowing whether a given mdev device has display support at all. It > seems that we cannot simply use the default display=auto because > libvirt

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

On Mon, 9 Apr 2018 12:35:10 +0200 Gerd Hoffmann wrote: > This little series adds three drivers, for demo-ing and testing vfio > display interface code. There is one mdev device for each interface > type (mdpy.ko for region and mbochs.ko for dmabuf). Erik Skultety brought up