From: Juergen Gross <jgross@suse.com>
To: David Vrabel <david.vrabel@citrix.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
konrad.wilk@oracle.com, boris.ostrovsky@oracle.com,
jbeulich@suse.com
Subject: Re: [Xen-devel] [PATCH V2 2/3] xen: eliminate scalability issues from initrd handling
Date: Wed, 17 Sep 2014 16:01:33 +0200 [thread overview]
Message-ID: <5419943D.7020105@suse.com> (raw)
In-Reply-To: <54199065.1020200@citrix.com>
On 09/17/2014 03:45 PM, David Vrabel wrote:
> On 17/09/14 05:12, Juergen Gross wrote:
>> Size restrictions native kernels wouldn't have resulted from the initrd
>> getting mapped into the initial mapping. The kernel doesn't really need
>> the initrd to be mapped, so use infrastructure available in Xen to avoid
>> the mapping and hence the restriction.
>>
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>> ---
>> arch/x86/xen/enlighten.c | 11 +++++++++--
>> arch/x86/xen/xen-head.S | 1 +
>> 2 files changed, 10 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
>> index c0cb11f..8fd075f 100644
>> --- a/arch/x86/xen/enlighten.c
>> +++ b/arch/x86/xen/enlighten.c
>> @@ -1519,6 +1519,7 @@ static void __init xen_pvh_early_guest_init(void)
>> asmlinkage __visible void __init xen_start_kernel(void)
>> {
>> struct physdev_set_iopl set_iopl;
>> + unsigned long initrd_start = 0;
>> int rc;
>>
>> if (!xen_start_info)
>> @@ -1667,10 +1668,16 @@ asmlinkage __visible void __init xen_start_kernel(void)
>> new_cpu_data.x86_capability[0] = cpuid_edx(1);
>> #endif
>>
>> + if (xen_start_info->mod_start)
>> + initrd_start = __pa(xen_start_info->mod_start);
>> +#ifdef CONFIG_BLK_DEV_INITRD
>> + if (xen_start_info->flags & SIF_MOD_START_PFN)
>> + initrd_start = PFN_PHYS(xen_start_info->mod_start);
>> +#endif
>
> Why the #ifdef?
>
> I'll fix this up to be:
>
> if (xen_start_info->mod_start) {
> if (xen_start_info->flags & SIF_MOD_START_PFN)
> initrd_start = PFN_PHYS_(xen_start_info->mod_start);
> else
> initrd_start = __pa(xen_start_info->mod_start);
> }
>
> Unless you object.
Yeah, you are right. This seems to be okay.
Juergen
next prev parent reply other threads:[~2014-09-17 14:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 4:12 [PATCH V2 0/3] xen: remove some memory limits from pv-domains Juergen Gross
2014-09-17 4:12 ` [PATCH V2 1/3] xen: sync some headers with xen tree Juergen Gross
2014-09-17 4:12 ` [PATCH V2 2/3] xen: eliminate scalability issues from initrd handling Juergen Gross
2014-09-17 13:45 ` [Xen-devel] " David Vrabel
2014-09-17 14:01 ` Juergen Gross [this message]
2014-09-17 4:12 ` [PATCH V2 3/3] xen: eliminate scalability issues from initial mapping setup Juergen Gross
2014-09-17 14:07 ` [Xen-devel] " David Vrabel
2014-09-17 14:17 ` Jan Beulich
2014-09-17 14:20 ` [Xen-devel] " Juergen Gross
2014-09-17 14:42 ` David Vrabel
2014-09-17 14:47 ` Juergen Gross
2014-09-17 14:43 ` [PATCH V2 0/3] xen: remove some memory limits from pv-domains David Vrabel
2014-09-17 14:48 ` Juergen Gross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5419943D.7020105@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jbeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).