[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel] RE: pv_ops polish: config option & head file



>> How about just simply use CONFIG_PARAVIRT ?
> 
>    Then how do you specify that you want a kernel built with Xen
> support, but not KVM?
> 

Mmm, this is kind of what level of detail do we want user to choose. 
Given that RHEL want one image, so this sub-option is just for
in house development even if multiple IA64 VMM really comes.
We can argu for the usage model.


Leaving some code for this is OK, but 
but at least for those who have running_on_xen condition already,
we don;t need CONFIG_XEN, (rather CONFIG_PARAVIRT).
Also for those Xen specific files, i.e. those xen wrapper code,
we can treat whole directory as one, either compile it or skip it.
Does this make sense?

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.