From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Huang, Ying" <ying.huang@intel.com>,
andi@firstfloor.org, mingo@redhat.com, tglx@linutronix.de,
Paul Jackson <pj@sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm 0/4] x86_64 boot: Add linked listof struct setup_data to boot protocol
Date: Thu, 27 Mar 2008 09:36:58 -0700 [thread overview]
Message-ID: <47EBCD2A.8010301@zytor.com> (raw)
In-Reply-To: <20080327094759.GB5056@elte.hu>
Ingo Molnar wrote:
> * Huang, Ying <ying.huang@intel.com> wrote:
>
>>> could you try to do that nevertheless? We generally prefer feature
>>> patches after sensible unification has been done.
>> I try to port reserve_early() to i386 before. But it is said that the
>> reserve_early() should be replaced by e820 based early
>> reservation/allocation mechanism on i386 and x86_64. So I think I
>> should wait for it.
>
> correct, e820 space manipulations is how it should be done. Peter, any
> progress on that project?
>
It's not all that complex of a piece of code, but the testing is painful
(fortunately, I have some code which has been at least partially
validated already.)
I have been working on a nonkernel project this week
(http://syslinux.zytor.com/archives/2008-March/009723.html), but I'm
hoping to look at it next week.
-hpa
prev parent reply other threads:[~2008-03-27 16:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 7:09 [PATCH -mm 0/4] x86_64 boot: Add linked listof struct setup_data to boot protocol Huang, Ying
2008-03-27 8:32 ` Ingo Molnar
2008-03-27 9:02 ` Paul Jackson
2008-03-27 9:09 ` Ingo Molnar
2008-03-27 9:21 ` Paul Jackson
2008-03-27 9:46 ` Ingo Molnar
2008-03-27 9:25 ` Huang, Ying
2008-03-27 9:47 ` Ingo Molnar
2008-03-27 16:36 ` H. Peter Anvin [this message]
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=47EBCD2A.8010301@zytor.com \
--to=hpa@zytor.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=pj@sgi.com \
--cc=tglx@linutronix.de \
--cc=ying.huang@intel.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 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.