From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Yinghai Lu <yinghai@kernel.org>, Ingo Molnar <mingo@elte.hu>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] x86: add brk allocation for very, very early allocations
Date: Fri, 27 Feb 2009 11:26:53 -0800 [thread overview]
Message-ID: <49A83E7D.1080508@goop.org> (raw)
In-Reply-To: <49A83C52.5050801@zytor.com>
H. Peter Anvin wrote:
> Jeremy Fitzhardinge wrote:
>
>> unsigned int boot_cpu_id __read_mostly;
>> +__initdata unsigned long _brk_start, _brk_end;
>>
>>
>
> Better yet, initialize _brk_start and _brk_end statically:
>
> extern const char _end[];
> __initdata unsigned long _brk_start = (unsigned long)&_end;
> __initdata unsigned long _brk_end = (unsigned long)&_end;
>
> That way it's available from the first instruction, and we can fully
> remove the x86-32 init_pg_tables_end and replace it with _brk_end (thus
> putting the initial page tables in the brk.)
Yes. It doesn't work for Xen (the domain builder puts the initrd and
Xen-built pagetable immediately after the kernel's bss), but its no
problem to move the brk in that case.
J
next prev parent reply other threads:[~2009-02-27 19:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 17:58 [PATCH RFC] x86: add brk allocation for very, very early allocations Jeremy Fitzhardinge
2009-02-27 18:43 ` H. Peter Anvin
2009-02-27 19:17 ` H. Peter Anvin
2009-02-27 19:26 ` Jeremy Fitzhardinge [this message]
2009-02-27 20:26 ` Yinghai Lu
2009-02-27 21:02 ` Jeremy Fitzhardinge
2009-02-27 21:05 ` H. Peter Anvin
2009-02-27 21:19 ` Jeremy Fitzhardinge
2009-02-27 21:28 ` H. Peter Anvin
2009-02-27 21:41 ` Jeremy Fitzhardinge
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=49A83E7D.1080508@goop.org \
--to=jeremy@goop.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.org \
--cc=yinghai@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.