Displaying 20 results from an estimated 21 matches for "r65777".
2013 Jul 02
2
binding/unbinding devices to vfio-pci
> -----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:
> > Alex,
> >
> > I'm trying to think through how binding/un...
2013 Jul 02
2
binding/unbinding devices to vfio-pci
> -----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:
> > Alex,
> >
> > I'm trying to think through how binding/un...
2013 Jul 16
1
RFC: vfio interface for platform devices
> -----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 interface for platform devices
>
> On 07/16/2013 04:51:12 PM, Yoder Stuart-B082...
2013 Jul 16
1
RFC: vfio interface for platform devices
> -----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 interface for platform devices
>
> On 07/16/2013 04:51:12 PM, Yoder Stuart-B082...
2013 Jul 03
0
RFC: vfio interface for platform devices
> -----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 devices
>
> On 07/02/2013 08:07:53 PM, Alexander Graf wr...
2013 Jul 03
1
RFC: vfio interface for platform devices
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
2013 Jul 03
1
RFC: vfio interface for platform devices
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
2013 Jul 16
2
RFC: vfio interface for platform devices
> -----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 interface for platform devices
>
> On 07/02/2013 06:25:59 PM, Yoder Stuart-B082...
2013 Jul 16
2
RFC: vfio interface for platform devices
> -----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 interface for platform devices
>
> On 07/02/2013 06:25:59 PM, Yoder Stuart-B082...
2011 Jun 21
6
[PATCH 00/02][RESEND] virtio: Virtio platform driver
virtio: Virtio platform driver
[PATCH 01/02] virtio: Break out lguest virtio code to virtio_lguest.c
[PATCH 02/02] virtio: Add virtio platform driver
These patches add a virtio platform driver to the Linux kernel. This
platform driver has the same role as the virtio_pci driver, but instead
of building on top of emulated PCI this driver is making use of the
platform bus together with driver
2011 Jun 21
6
[PATCH 00/02][RESEND] virtio: Virtio platform driver
virtio: Virtio platform driver
[PATCH 01/02] virtio: Break out lguest virtio code to virtio_lguest.c
[PATCH 02/02] virtio: Add virtio platform driver
These patches add a virtio platform driver to the Linux kernel. This
platform driver has the same role as the virtio_pci driver, but instead
of building on top of emulated PCI this driver is making use of the
platform bus together with driver
2013 Jul 02
2
binding/unbinding devices to vfio-pci
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
2013 Jul 02
2
binding/unbinding devices to vfio-pci
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
2014 Aug 20
2
[RFC PATCH 00/11] Refactor MSI to support Non-PCI device
> -----Original Message-----
> From: linux-pci-owner at vger.kernel.org [mailto:linux-pci-owner at vger.kernel.org]
> On Behalf Of Yijing Wang
> Sent: Wednesday, August 20, 2014 11:59 AM
> To: Bhushan Bharat-R65777; Basu Arnab-B45036
> Cc: Xinwei Hu; Wuyun; Bjorn Helgaas; linux-pci at vger.kernel.org;
> Paul.Mundt at huawei.com; James E.J. Bottomley; Marc Zyngier; linux-arm-
> kernel at lists.infradead.org; Russell King; linux-arch at vger.kernel.org;
> virtualization at lists.linux-foundation.org...
2014 Aug 20
2
[RFC PATCH 00/11] Refactor MSI to support Non-PCI device
> -----Original Message-----
> From: linux-pci-owner at vger.kernel.org [mailto:linux-pci-owner at vger.kernel.org]
> On Behalf Of Yijing Wang
> Sent: Wednesday, August 20, 2014 11:59 AM
> To: Bhushan Bharat-R65777; Basu Arnab-B45036
> Cc: Xinwei Hu; Wuyun; Bjorn Helgaas; linux-pci at vger.kernel.org;
> Paul.Mundt at huawei.com; James E.J. Bottomley; Marc Zyngier; linux-arm-
> kernel at lists.infradead.org; Russell King; linux-arch at vger.kernel.org;
> virtualization at lists.linux-foundation.org...
2014 Aug 20
2
[RFC PATCH 00/11] Refactor MSI to support Non-PCI device
Hi Yijing
> -----Original Message-----
> From: linux-pci-owner at vger.kernel.org [mailto:linux-pci-owner at vger.kernel.org]
> On Behalf Of Yijing Wang
> Sent: Monday, August 04, 2014 8:34 AM
> To: Basu Arnab-B45036
> Cc: Xinwei Hu; Wuyun; Bjorn Helgaas; linux-pci at vger.kernel.org;
> Paul.Mundt at huawei.com; James E.J. Bottomley; Marc Zyngier; linux-arm-
> kernel at
2014 Aug 20
2
[RFC PATCH 00/11] Refactor MSI to support Non-PCI device
Hi Yijing
> -----Original Message-----
> From: linux-pci-owner at vger.kernel.org [mailto:linux-pci-owner at vger.kernel.org]
> On Behalf Of Yijing Wang
> Sent: Monday, August 04, 2014 8:34 AM
> To: Basu Arnab-B45036
> Cc: Xinwei Hu; Wuyun; Bjorn Helgaas; linux-pci at vger.kernel.org;
> Paul.Mundt at huawei.com; James E.J. Bottomley; Marc Zyngier; linux-arm-
> kernel at
2013 Jul 03
6
RFC: vfio interface for platform devices (v2)
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
2013 Jul 03
6
RFC: vfio interface for platform devices (v2)
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
2013 Jul 02
7
RFC: vfio interface for platform devices
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