From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: [PATCH RFC v1 09/13] elfnotes: intorduce a new PHYS_ENTRY elfnote Date: Tue, 23 Jun 2015 11:01:20 +0100 Message-ID: <55894A900200007800088129@mail.emea.novell.com> References: <1434989487-74940-1-git-send-email-roger.pau@citrix.com> <1434989487-74940-10-git-send-email-roger.pau@citrix.com> <55894466020000780008807B@mail.emea.novell.com> <55892994.9000203@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Z7L1A-000393-U3 for xen-devel@lists.xenproject.org; Tue, 23 Jun 2015 10:01:25 +0000 In-Reply-To: <55892994.9000203@citrix.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: =?UTF-8?Q?Roger=20Pau=20Monn=C3=A9?= Cc: Elena Ufimtseva , Wei Liu , Ian Campbell , Stefano Stabellini , Andrew Cooper , Ian Jackson , xen-devel@lists.xenproject.org, BorisOstrovsky List-Id: xen-devel@lists.xenproject.org >>> On 23.06.15 at 11:40, wrote: > El 23/06/15 a les 11.35, Jan Beulich ha escrit: >>>>> On 22.06.15 at 18:11, wrote: >>> @@ -213,6 +214,9 @@ elf_errorstatus elf_xen_parse_note(struct elf_binary > *elf, >>> elf, note, sizeof(*parms->f_supported), i); >>> break; >>> >>> + case XEN_ELFNOTE_PHYS_ENTRY: >>> + parms->phys_entry = val; >> >> I don't think I've seen this field having got added in an earlier patch, >> and it's also not getting added here. > > Yes, it's added in patch 5, because it's also used by the HVM-generic > loader. So indeed missed it (being in an otherwise tools only patch). Sorry. >>> --- a/xen/include/public/elfnote.h >>> +++ b/xen/include/public/elfnote.h >>> @@ -200,9 +200,18 @@ >>> #define XEN_ELFNOTE_SUPPORTED_FEATURES 17 >>> >>> /* >>> + * Physical entry point into the kernel. >>> + * >>> + * 32bit entry point into the kernel. Xen will use this entry point >>> + * in order to launch the guest kernel in 32bit protected mode >>> + * with paging disabled. >>> + */ >>> +#define XEN_ELFNOTE_PHYS_ENTRY 18 >> >> Perhaps XEN_ELFNOTE_PHYS_ENTRY32 or XEN_ELFNOTE_PHYS32_ENTRY >> then? > > That's fine, I don't mind changing it. Although AFAIK it's not possible > to have a 64bit physical entry point (paging-disabled). That depends on the perspective you take: Under UEFI the kernel would be entered in pseudo-physical (1:1 mapped virtual) mode. And that's certainly a model to at least keep in mind. Jan