[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 2/2] xen: make start_info x86 specific.
On Fri, 2013-02-15 at 13:41 +0000, Jan Beulich wrote: > >>> On 15.02.13 at 14:24, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote: > > All I actually care about is the removal of struct start_info from the > > canonical copy of the hypervisor ABI (that is xen/include/public) for > > ARM. > > But as already said - to me this looks wrong. The structure has > generally useful fields (and unless ARM uses _none_ of them, This is right, ARM uses none of them, at the hypervisor ABI level at least. There's actually no way to pass a start info to an ARM guest because they are launched via the native code paths. > then it must have some other way to communicate the respective > stuff, in which case I'd ask why a second mechanism got invented > when there already was one available), and even more so from > the abstract PV perspective. ARM uses HVM params (e.g. the xenstore and console ring + evtchn) and XENFEAT_dom0 etc (for privilegedness). I guess it is obvious why HVM params were needed on HVM and you invented XENFEAT_dom0 IIRC :-) Ian. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |