public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "Huang, Ying" <ying.huang@intel.com>, 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: Sat, 22 Sep 2007 12:56:12 -0700	[thread overview]
Message-ID: <46F5735C.5040803@zytor.com> (raw)
In-Reply-To: <46F53848.3030100@goop.org>

Jeremy Fitzhardinge wrote:
> 
> Do you actually need a linked list of data?  This is similar to the
> changes to bzImage to support booting bzImage a paravirt environment,
> but I just proposed a pointer to a single info structure, along with a
> field to identify the boot environment (ie, native/lguest/xen etc).  It
> would be easy to extend this to handle EFI as just another boot
> environment, and you could hang a list of structures off the pointer.
> 

*He* doesn't, but *we* do.  We have already run into at least one case
where the existing structure is insufficient (EDD overhaul), and so we
need to do something extensible.

	-hpa

      reply	other threads:[~2007-09-22 19:56 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
2007-09-28 22:28     ` H. Peter Anvin
2007-09-22 15:44 ` Jeremy Fitzhardinge
2007-09-22 19:56   ` 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=46F5735C.5040803@zytor.com \
    --to=hpa@zytor.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mouli@linux.intel.com \
    --cc=yhlu.kernel@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox