From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?windows-1252?Q?Roger_Pau_Monn=E9?= Subject: Re: [PATCH v3 31/32] libxc: switch xc_dom_elfloader to be used with HVMlite domains Date: Thu, 23 Jul 2015 12:48:51 +0200 Message-ID: <55B0C693.9030309@citrix.com> References: <1435923310-9019-1-git-send-email-roger.pau@citrix.com> <1435923310-9019-32-git-send-email-roger.pau@citrix.com> <20150710190737.GG30788@l.oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1ZIE3e-0002Hp-Mj for xen-devel@lists.xenproject.org; Thu, 23 Jul 2015 10:48:58 +0000 In-Reply-To: <20150710190737.GG30788@l.oracle.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: xen-devel@lists.xenproject.org, Ian Campbell , Wei Liu , Ian Jackson , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org El 10/07/15 a les 21.07, Konrad Rzeszutek Wilk ha escrit: > On Fri, Jul 03, 2015 at 01:35:09PM +0200, Roger Pau Monne wrote: >> Allow xc_dom_elfloader to report a guest type as hvm-3.0-x86_32 if it's >> running inside of a HVM container and has the PHYS32_ENTRY elfnote set. >> >> Signed-off-by: Roger Pau Monn=E9 >> Cc: Ian Jackson >> Cc: Stefano Stabellini >> Cc: Ian Campbell >> Cc: Wei Liu >> --- >> Only xc_dom_elfloader has been switched to support HVMlite, other loaders >> should also be switched once we have a HVMlite compatible kernel that us= es >> them. >> --- >> tools/libxc/xc_dom_elfloader.c | 4 ++++ >> 1 file changed, 4 insertions(+) >> >> diff --git a/tools/libxc/xc_dom_elfloader.c b/tools/libxc/xc_dom_elfload= er.c >> index 6ce1062..2f05015 100644 >> --- a/tools/libxc/xc_dom_elfloader.c >> +++ b/tools/libxc/xc_dom_elfloader.c >> @@ -57,6 +57,10 @@ static char *xc_dom_guest_type(struct xc_dom_image *d= om, >> { >> uint64_t machine =3D elf_uval(elf, elf->ehdr, e_machine); >> = >> + if ( dom->container_type =3D=3D XC_DOM_HVM_CONTAINER && >> + dom->parms.phys_entry !=3D UNSET_ADDR ) >> + return "hvm-3.0-x86_32"; > = > why not 'hvm-lite-1.0-x86_64' since it is new protocol? Because it shares the code paths with the HVM builder. We could introduce a new type, but I don't see any value in doing it, it's just going to be a copy of hvm-3.0-x86_32. Roger.