[Xen-ia64-devel] [PATCH 0/5] guest_os_type

[Alex Williamson <alex.williamson@xxxxxx>]

   I took Wing's guest_os_type patch and reimplemented it to match more
what I was thinking.  The HVM_PARAM_GOS_TYPE value is an encoded version
of the guest_os_type string, allowing more flexibility and less common
code maintenance.  I see now why Wing decided not to use
HYPERVISOR_opt_feature as it only allows setting features on the current
domain.  Rather than add a flag to XEN_DOMCTL_arch_setup, I thought a
separate domctl might make this a little cleaner and add more
flexibility in the builder code.

   The first 2 patches will be sent to xen-devel, the last 3 can go in
via the ia64 tree once the first 2 are there.  Please let me know if
this approach looks reasonable.  Wing, Rongui, I'd be happy to add a
Signed-off-by/Acked-by line for you since much of this is leveraged from
your work.  Thanks,

        Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.


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