From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
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 13:28:24 -0800 [thread overview]
Message-ID: <49A85AF8.8030009@zytor.com> (raw)
In-Reply-To: <49A858E8.3070707@goop.org>
Jeremy Fitzhardinge wrote:
>
>> This reminds me... is your intent that the BRK is permanent (unless
>> explicitly freed on a page by page basis) or part of the init memory
>> that is flushed?
>
> Permanent. I'm using it to allocate things which are the moral
> equivalent of the kernel pagetables.
>
Cool; just wanted it noted what the rules were. Even more so the reason
to fold as many possible uses as possible into this new mechanism.
-hpa
P.S. Could you send me the updates to the dom0 patches you said you had?
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-02-27 21:31 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
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 [this message]
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=49A85AF8.8030009@zytor.com \
--to=hpa@zytor.com \
--cc=jeremy@goop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox