Re: [Xen-devel] [PATCH 14 of 32 RFC] libxl: HVM device configuration info build_info->u.hvm

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Mon, 2012-01-16 at 16:53 +0000, Ian Jackson wrote:
> Ian Campbell writes ("Re: [Xen-devel] [PATCH 14 of 32 RFC] libxl: HVM device 
> configuration info build_info->u.hvm"):
> > While we are at it -- do you have any thoughts on how per-arch options
> > should be handled? I was thinking of adding the possibility in the IDL
> > to tag a field with a list of architectures?
> 
> If we eventually tunnel these structures over some kind of IPC
> mechanism it might be necessary to deal with values from other than
> the native architecture.

Hrm, yes.

> So perhaps per-arch fields should exist in every version and just have
> the arch in their name somehow, although that wouldn't spot people
> setting them inappropriately.
> 
> Alternative a variadic substructure where _init sets the enum to the
> default native arch ?

I wonder if these all fit into the existing build_info.u.{hvm,pv}. e.g.
if we shouldn't have hvm_x86,pv_x86,arm etc instead?

Another alternative is to do like we do for for foreign structures in
the hypervisor and generate compat versions of each struct as well as
native ones (e.g. libxl_x86_...).

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel