search for: devtree

...> needs to be passed by the user (granted, this will not be the case for > ever). So I think even if we treat them the same in code, we should be > discussing them separately. We do need to keep core resources separate from what it takes to generate a guest DT, but note the purpose of the devtree info is not primarily to help generate a guest DT. User space (not just QEMU) needs to know what the regions and interrupts advertised by DEVICE_GET_INFO correspond to. If there are 4 interrupts and 2 register regions, how does user space know the purpose/function of each? Apart from something lik...

....com> wrote: > On Tue, 2013-07-02 at 23:25 +0000, 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 corresponding >> device tree node structure that is defined for most platform devices. >> >> Regards, >> Stuart Yoder >> >> ----------------------------------------------------------...

....com> wrote: > On Tue, 2013-07-02 at 23:25 +0000, 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 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 ------------------------------------------------------------------------------ VFIO for Platform Devices The existing...

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 ------------------------------------------------------------------------------ VFIO for Platform Devices The existing...

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 the > corresponding > device tree node structure that is defined for most platform devices. > > Regards, > Stuart Yoder > > -----------------------------------------------------------------------------...

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 corresponding > device tree node structure that is defined for most platform devices. > > Regards, > Stuart Yoder > > ------------------------------------------------------------------------------ >...

On Tue, 2013-07-02 at 23:25 +0000, 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 corresponding > device tree node structure that is defined for most platform devices. > > Regards, > Stuart Yoder > > ------------------------------------------------------------------------------ >...

...ces > > 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 the > > corresponding > > device tree node structure that is defined for most platform devices. > > > > Regards, > > Stuart Yoder > > > > -----------------------------------------...

...ces > > 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 the > > corresponding > > device tree node structure that is defined for most platform devices. > > > > Regards, > > Stuart Yoder > > > > -----------------------------------------...

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 associated struct -removed redundant example ---------------------------...

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 associated struct -removed redundant example ---------------------------...

On Wed, 2013-07-03 at 21:40 +0000, 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, > defined 5 new flags and associated structs > -VFIO_DEVICE_GET_IRQ_INFO-- updated as per AlexW's suggestion, > defined 1 new flag and associated struct > -removed redundant example &gt...

Hi Ewan, I''m almost ready to integrate some PPC-specific stuff into xend, and I was wondering if you had a plan for how that should work. First example: the device tree data structure we talked about a few weeks ago. We will need to pass the config data to PPC code, probably in XendDomainInfo.initDomain(), and then pass the resulting data structure into libxc''s xc_linux_load()

Hi, This is the fifth version of this patch series. With the Versatile Express TC2, it''s possible to boot only with A7 or A15. If the user choose to boot with only A7, the CPU ID will start at 0x100. As Xen relies on it to set the logical ID and the GIC, it won''t be possible to use Xen with this use case. This patch series is divided in 3 parts: - Patch 1: prepare Xen