[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-ia64-devel][PATCH][VTD][dom0] dom0 vtd patch
Isaku Yamahata wrote: > On Wed, Oct 22, 2008 at 05:43:13PM +0800, Xu, Anthony wrote: >> dom0/ia64/vtd patch >> >> Signed-off-by: Anthony Xu <anthony.xu@xxxxxxxxx> > > > In XEN_DOMCTL_get_device_group case. > > > struct xen_domctl_get_device_group { > uint32_t machine_bdf; /* IN */ > uint32_t max_sdevs; /* IN */ > uint32_t num_sdevs; /* OUT */ > XEN_GUEST_HANDLE_64(uint32) sdev_array; /* OUT */ > }; > > XEN_DOMCTL_get_device_group is used by libxc. > sdev_array needs ot be handled correctly. I guess you are talking about xencomm, I don't know how to handle it. Can you enlighten me? Thanks, anthony > > >> dom0/ia64/vtd patch >> >> Signed-off-by: Anthony Xu <anthony.xu@xxxxxxxxx> >> >> >> diff -r 16c549b3ba59 arch/ia64/xen/xcom_privcmd.c >> --- a/arch/ia64/xen/xcom_privcmd.c Tue Oct 14 14:58:08 2008 +0100 >> +++ b/arch/ia64/xen/xcom_privcmd.c Wed Oct 22 17:15:56 2008 +0800 >> @@ -354,6 +354,14 @@ case XEN_DOMCTL_set_opt_feature: >> case XEN_DOMCTL_assign_device: >> case XEN_DOMCTL_subscribe: >> + case XEN_DOMCTL_get_device_group: >> + case XEN_DOMCTL_test_assign_device: >> + case XEN_DOMCTL_deassign_device: >> + case XEN_DOMCTL_bind_pt_irq: >> + case XEN_DOMCTL_unbind_pt_irq: >> + case XEN_DOMCTL_memory_mapping: >> + case XEN_DOMCTL_ioport_mapping: >> + >> break; >> case XEN_DOMCTL_pin_mem_cacheattr: >> return -ENOSYS; _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-ia64-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |