public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Huang, Ying" <ying.huang@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andi Kleen <ak@suse.de>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	akpm@linux-foundation.org, Yinghai Lu <yhlu.kernel@gmail.com>,
	Chandramouli Narayanan <mouli@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm -v3 1/2] i386/x86_64 boot: setup data
Date: Thu, 27 Sep 2007 14:06:40 +0800	[thread overview]
Message-ID: <1190873200.21818.292.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <46F14896.8080603@zytor.com>

Hi, Peter,

On Wed, 2007-09-19 at 09:04 -0700, H. Peter Anvin wrote:
> Huang, Ying wrote:
> > 
> > Known Issues:
> > 
> > 1. Where is safe to place the linked list of setup_data?
> > Because the length of the linked list of setup_data is variable, it
> > can not be copied into BSS segment of kernel as that of "zero
> > page". We must find a safe place for it, where it will not be
> > overwritten by kernel during booting up. The i386 kernel will
> > overwrite some pages after _end. The x86_64 kernel will overwrite some
> > pages from 0x1000 on.
> > 
> 
> The latter is definitely not safe, since the space below 640K is the
> documented place to put the command line (and presumably where the
> bootloader would put other auxilliary chunks.)
> 
> I'll try to do a full review of this later today.  Haven't had time yet
> to look at this anything than but piecemeal.

Do you think this patch and the 32-bit boot protocol patch are ready to
merge for -mm? If not, I can revise them.

Best Regards,
Huang Ying

  reply	other threads:[~2007-09-27  6:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19  8:58 [PATCH -mm -v3 1/2] i386/x86_64 boot: setup data Huang, Ying
2007-09-19 16:04 ` H. Peter Anvin
2007-09-27  6:06   ` Huang, Ying [this message]
2007-09-28 22:28     ` H. Peter Anvin
2007-09-22 15:44 ` Jeremy Fitzhardinge
2007-09-22 19:56   ` H. Peter Anvin

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=1190873200.21818.292.camel@caritas-dev.intel.com \
    --to=ying.huang@intel.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mouli@linux.intel.com \
    --cc=yhlu.kernel@gmail.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