From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [Xen-devel] [PATCH 2/3] xen: eliminate scalability issues from initrd handling Date: Thu, 4 Sep 2014 15:53:23 +0100 Message-ID: <54087CE3.6020400@citrix.com> References: <1409834326-29287-1-git-send-email-jgross@suse.com> <1409834326-29287-3-git-send-email-jgross@suse.com> <5408607F.6020108@citrix.com> <540893570200007800030E4C@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <540893570200007800030E4C@mail.emea.novell.com> Sender: linux-kernel-owner@vger.kernel.org To: Jan Beulich , David Vrabel Cc: Juergen Gross , boris.ostrovsky@oracle.com, xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org List-Id: xen-devel@lists.xenproject.org On 04/09/14 15:29, Jan Beulich wrote: >>>> On 04.09.14 at 14:52, wrote: >> On 04/09/14 13:38, Juergen Gross wrote: >>> --- a/arch/x86/xen/xen-head.S >>> +++ b/arch/x86/xen/xen-head.S >>> @@ -124,6 +124,9 @@ NEXT_HYPERCALL(arch_6) >>> ELFNOTE(Xen, XEN_ELFNOTE_L1_MFN_VALID, >>> .quad _PAGE_PRESENT; .quad _PAGE_PRESENT) >>> ELFNOTE(Xen, XEN_ELFNOTE_SUSPEND_CANCEL, .long 1) >>> +#ifdef CONFIG_X86_64 >>> + ELFNOTE(Xen, XEN_ELFNOTE_MOD_START_PFN, .long 1) >>> +#endif >> >> Why X86_64 only? If there's a good reason the commit message needs to >> explain why. > > Does native 32-bit support huge initrd? Does that matter? If the MOD_START_PFN options works with a 32-bit guest then it should use it, regardless of whether it is essential or not. Because this reduces the #ifdef'ery. David