public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: virtualization@lists.osdl.org, Andrew Morton <akpm@osdl.org>,
	Ian Pratt <ian.pratt@xensource.com>,
	Xen-devel <xen-devel@lists.xensource.com>,
	Chris Wright <chrisw@sous-sol.org>,
	Christoph Lameter <clameter@sgi.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH 8 of 13] Add a bootparameter to reserve high linear address space for hypervisors
Date: 02 Aug 2006 04:59:32 +0200	[thread overview]
Message-ID: <p73lkq7zvu3.fsf@verdi.suse.de> (raw)
In-Reply-To: <1154479684.2570.14.camel@localhost.localdomain>

Rusty Russell <rusty@rustcorp.com.au> writes:
> 
> I only implemented parse_early_param two years ago; maybe it is time for
> i386 to use it...

Problem is that it's too late. Some of the stuff is already needed
in setup_arch. You would need to move it before it first.

Unfortunately touching the order might cause very subtle problem
on other architectures - this tends to be fragile.

-Andi

  reply	other threads:[~2006-08-02  2:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0adfc39039c79e4f4121.1154462446@ezr>
2006-08-01 21:47 ` [PATCH 8 of 13] Add a bootparameter to reserve high linear address space for hypervisors Andi Kleen
2006-08-02  0:48   ` Rusty Russell
2006-08-02  2:59     ` Andi Kleen [this message]
2006-08-02  3:54       ` [Xen-devel] " Rusty Russell
2006-08-02  4:21         ` Andi Kleen
2006-08-02  4:33           ` Rusty Russell
2006-08-02  4:36             ` Andi Kleen
2006-08-02  5:20               ` Rusty Russell
2006-08-02  5:24                 ` Andi Kleen
2006-08-02  9:06                   ` [PATCH 1/2] Allow early_param and identical __setup to exist Rusty Russell
2006-08-02  9:08                   ` [PATCH 2/2] Replace i386 open-coded cmdline parsing with early_param/parse_early_param Rusty Russell
2006-08-02  9:24                     ` Andi Kleen

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=p73lkq7zvu3.fsf@verdi.suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=chrisw@sous-sol.org \
    --cc=clameter@sgi.com \
    --cc=ebiederm@xmission.com \
    --cc=ian.pratt@xensource.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=virtualization@lists.osdl.org \
    --cc=xen-devel@lists.xensource.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