[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <540893570200007800030E4C@mail.emea.novell.com>
Date: Thu, 04 Sep 2014 15:29:11 +0100
From: "Jan Beulich" <JBeulich@...e.com>
To: "David Vrabel" <david.vrabel@...rix.com>
Cc: <xen-devel@...ts.xensource.com>, <boris.ostrovsky@...cle.com>,
<konrad.wilk@...cle.com>, "Juergen Gross" <JGross@...e.com>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/3] xen: eliminate scalability issues from initrd
handling
>>> On 04.09.14 at 14:52, <david.vrabel@...rix.com> 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?
Jan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists