From: Andi Kleen <ak@suse.de>
To: vgoyal@in.ibm.com
Subject: Re: [Fastboot] [PATCH][RFC] x86_64: Reload CS when startup_64 is used.
Date: Mon, 21 Aug 2006 17:04:03 +0200
User-Agent: KMail/1.9.3
Cc: Magnus Damm <magnus.damm@gmail.com>, Magnus Damm <magnus@valinux.co.jp>,
       fastboot@lists.osdl.org, linux-kernel@vger.kernel.org,
       ebiederm@xmission.com
References: <20060821095328.3132.40575.sendpatchset@cherry.local> <200608211624.11005.ak@suse.de> <20060821144657.GE9549@in.ibm.com>
In-Reply-To: <20060821144657.GE9549@in.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200608211704.03061.ak@suse.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1029
Lines: 25

On Monday 21 August 2006 16:46, Vivek Goyal wrote:
> On Mon, Aug 21, 2006 at 04:24:10PM +0200, Andi Kleen wrote:
> > 
> > > Given the idea of relocatable kernel is floating around I would prefer if
> > > we are not bounded by the restriction of loading a kernel in lowest 4G.
> > 
> > There is already other code that requires this. In fact i don't think it can
> > be above 40MB currently.
> >
> 
> But I think Eric's prototype patches for relocatable kernel do get over
> this limitation (Hope I understood the code right). Assuming that relocatable
> kernel patches will be merged down the line, it would be nice not to be
> bound by 4G limitation.

He may have fixed the 40MB issue, but I very much doubt he changed the 2GB
limitation because that would be a major change.

-Andi

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/