search for: b08248

> -----Original Message----- > From: Alex Williamson [mailto:alex.williamson at redhat.com] > Sent: Tuesday, July 02, 2013 9:46 AM > To: Yoder Stuart-B08248 > Cc: kvm at vger.kernel.org list; Alexander Graf; Bhushan Bharat-R65777; a.motakis at virtualopensystems.com; > virtualization at lists.linux-foundation.org > Subject: Re: binding/unbinding devices to vfio-pci > > On Tue, 2013-07-02 at 14:15 +0000, Yoder Stuart-B08248 wrote: > &...

> -----Original Message----- > From: Alex Williamson [mailto:alex.williamson at redhat.com] > Sent: Tuesday, July 02, 2013 9:46 AM > To: Yoder Stuart-B08248 > Cc: kvm at vger.kernel.org list; Alexander Graf; Bhushan Bharat-R65777; a.motakis at virtualopensystems.com; > virtualization at lists.linux-foundation.org > Subject: Re: binding/unbinding devices to vfio-pci > > On Tue, 2013-07-02 at 14:15 +0000, Yoder Stuart-B08248 wrote: > &...

> -----Original Message----- > From: Wood Scott-B07421 > Sent: Tuesday, July 16, 2013 5:01 PM > To: Yoder Stuart-B08248 > Cc: Wood Scott-B07421; Alex Williamson; Alexander Graf; Bhushan Bharat-R65777; Sethi Varun-B16395; > virtualization at lists.linux-foundation.org; Antonios Motakis; kvm at vger.kernel.org list; kvm- > ppc at vger.kernel.org; kvmarm at lists.cs.columbia.edu > Subject: Re: RFC: vfio int...

> -----Original Message----- > From: Wood Scott-B07421 > Sent: Tuesday, July 16, 2013 5:01 PM > To: Yoder Stuart-B08248 > Cc: Wood Scott-B07421; Alex Williamson; Alexander Graf; Bhushan Bharat-R65777; Sethi Varun-B16395; > virtualization at lists.linux-foundation.org; Antonios Motakis; kvm at vger.kernel.org list; kvm- > ppc at vger.kernel.org; kvmarm at lists.cs.columbia.edu > Subject: Re: RFC: vfio int...

On 07/02/2013 08:07:53 PM, Alexander Graf wrote: > > On 03.07.2013, at 01:25, Yoder Stuart-B08248 wrote: > > > 8. Open Issues > > > > -how to handle cases where VFIO is requested to handle > > a device where the valid, mappable range for a region > > is less than a page size. See example above where an > > advertised region in the DMA node i...

On 07/02/2013 08:07:53 PM, Alexander Graf wrote: > > On 03.07.2013, at 01:25, Yoder Stuart-B08248 wrote: > > > 8. Open Issues > > > > -how to handle cases where VFIO is requested to handle > > a device where the valid, mappable range for a region > > is less than a page size. See example above where an > > advertised region in the DMA node i...

> -----Original Message----- > From: Wood Scott-B07421 > Sent: Wednesday, July 03, 2013 5:32 PM > To: Yoder Stuart-B08248 > Cc: Alex Williamson; Alexander Graf; Wood Scott-B07421; Bhushan Bharat-R65777; Sethi Varun-B16395; > virtualization at lists.linux-foundation.org; Antonios Motakis; kvm at vger.kernel.org list; kvm- > ppc at vger.kernel.org; kvmarm at lists.cs.columbia.edu > Subject: Re: RFC: vfio int...

> -----Original Message----- > From: Wood Scott-B07421 > Sent: Wednesday, July 03, 2013 5:32 PM > To: Yoder Stuart-B08248 > Cc: Alex Williamson; Alexander Graf; Wood Scott-B07421; Bhushan Bharat-R65777; Sethi Varun-B16395; > virtualization at lists.linux-foundation.org; Antonios Motakis; kvm at vger.kernel.org list; kvm- > ppc at vger.kernel.org; kvmarm at lists.cs.columbia.edu > Subject: Re: RFC: vfio int...

Alex, I'm trying to think through how binding/unbinding of devices will work with VFIO for platform devices and have a couple of questions about how vfio-pci works. When you bind a device to vfio-pci, e.g.: # echo 1102 0002 > /sys/bus/pci/drivers/vfio-pci/new_id ...I understand that the echo into 'new_id' tells the vfio pci driver that it now handles the specified PCI ID. But

Alex, I'm trying to think through how binding/unbinding of devices will work with VFIO for platform devices and have a couple of questions about how vfio-pci works. When you bind a device to vfio-pci, e.g.: # echo 1102 0002 > /sys/bus/pci/drivers/vfio-pci/new_id ...I understand that the echo into 'new_id' tells the vfio pci driver that it now handles the specified PCI ID. But

> -----Original Message----- > From: Wood Scott-B07421 > Sent: Wednesday, July 03, 2013 1:52 PM > To: Alexander Graf > Cc: Yoder Stuart-B08248; Alex Williamson; Wood Scott-B07421; Bhushan Bharat-R65777; Sethi Varun-B16395; > virtualization at lists.linux-foundation.org; Antonios Motakis; kvm at vger.kernel.org list; kvm- > ppc at vger.kernel.org; kvmarm at lists.cs.columbia.edu > Subject: Re: RFC: vfio interface for platform devi...

On Tue, 2013-07-02 at 14:15 +0000, Yoder Stuart-B08248 wrote: > Alex, > > I'm trying to think through how binding/unbinding of devices will > work with VFIO for platform devices and have a couple of questions > about how vfio-pci works. > > When you bind a device to vfio-pci, e.g.: > # echo 1102 0002 > /sys/bus/pci/driv...

On 07/16/2013 04:51:12 PM, Yoder Stuart-B08248 wrote: > > > 3. VFIO_DEVICE_GET_REGION_INFO > > > > > > No changes needed, except perhaps adding a new flag. Freescale > > > has some > > > devices with regions that must be mapped cacheable. > > > > While I don't object to making...

The write-up below is the first draft of a proposal for how the kernel can expose platform devices to user space using vfio. In short, I'm proposing a new ioctl VFIO_DEVICE_GET_DEVTREE_INFO which allows user space to correlate regions and interrupts to the corresponding device tree node structure that is defined for most platform devices. Regards, Stuart Yoder

The write-up below is the first draft of a proposal for how the kernel can expose platform devices to user space using vfio. In short, I'm proposing a new ioctl VFIO_DEVICE_GET_DEVTREE_INFO which allows user space to correlate regions and interrupts to the corresponding device tree node structure that is defined for most platform devices. Regards, Stuart Yoder

On 07/02/2013 06:25:59 PM, Yoder Stuart-B08248 wrote: > The write-up below is the first draft of a proposal for how the > kernel can expose > platform devices to user space using vfio. > > In short, I'm proposing a new ioctl VFIO_DEVICE_GET_DEVTREE_INFO which > allows user space to correlate regions and interrupts to th...

Version 2 -VFIO_GROUP_GET_DEVICE_FD-- specified that the path is a sysfs path -VFIO_DEVICE_GET_INFO-- defined 2 flags instead of 1 -deleted VFIO_DEVICE_GET_DEVTREE_INFO ioctl -VFIO_DEVICE_GET_REGION_INFO-- updated as per AlexW's suggestion, defined 5 new flags and associated structs -VFIO_DEVICE_GET_IRQ_INFO-- updated as per AlexW's suggestion, defined 1 new flag and

Version 2 -VFIO_GROUP_GET_DEVICE_FD-- specified that the path is a sysfs path -VFIO_DEVICE_GET_INFO-- defined 2 flags instead of 1 -deleted VFIO_DEVICE_GET_DEVTREE_INFO ioctl -VFIO_DEVICE_GET_REGION_INFO-- updated as per AlexW's suggestion, defined 5 new flags and associated structs -VFIO_DEVICE_GET_IRQ_INFO-- updated as per AlexW's suggestion, defined 1 new flag and

I'm having trouble understanding how this works where the Guest Device Model != Host. How do you inform the guest where the device is mapped in its physical address space, and handle GPA faults? - Mario On 7/3/2013 11:40 PM, Yoder Stuart-B08248 wrote: > Version 2 > -VFIO_GROUP_GET_DEVICE_FD-- specified that the path is a sysfs path > -VFIO_DEVICE_GET_INFO-- defined 2 flags instead of 1 > -deleted VFIO_DEVICE_GET_DEVTREE_INFO ioctl > -VFIO_DEVICE_GET_REGION_INFO-- updated as per AlexW's suggestion, > define...

On 03.07.2013, at 01:25, Yoder Stuart-B08248 wrote: > The write-up below is the first draft of a proposal for how the kernel can expose > platform devices to user space using vfio. > > In short, I'm proposing a new ioctl VFIO_DEVICE_GET_DEVTREE_INFO which > allows user space to correlate regions and interrupts to the corr...