From: Vivek Goyal <vgoyal@in.ibm.com>
To: Andi Kleen <ak@suse.de>
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
Subject: Re: [Fastboot] [PATCH][RFC] x86_64: Reload CS when startup_64 is used.
Date: Mon, 21 Aug 2006 10:46:57 -0400 [thread overview]
Message-ID: <20060821144657.GE9549@in.ibm.com> (raw)
In-Reply-To: <200608211624.11005.ak@suse.de>
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.
Thanks
Vivek
next prev parent reply other threads:[~2006-08-21 14:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 9:54 [PATCH][RFC] x86_64: Reload CS when startup_64 is used Magnus Damm
2006-08-21 10:19 ` Andi Kleen
2006-08-21 13:29 ` [Fastboot] " Magnus Damm
2006-08-21 14:16 ` Andi Kleen
2006-08-22 0:47 ` Magnus Damm
2006-08-21 14:17 ` Vivek Goyal
2006-08-21 14:24 ` Andi Kleen
2006-08-21 14:46 ` Vivek Goyal [this message]
2006-08-21 15:04 ` Andi Kleen
2006-08-21 20:02 ` Eric W. Biederman
2006-08-21 20:10 ` Andi Kleen
2006-08-21 21:00 ` Eric W. Biederman
2006-08-21 21:02 ` Eric W. Biederman
2006-08-22 0:58 ` Magnus Damm
2006-08-22 3:41 ` Eric W. Biederman
2006-08-22 4:10 ` Magnus Damm
2006-08-22 8:03 ` Andi Kleen
2006-08-22 8:37 ` [PATCH] " Eric W. Biederman
2006-08-22 8:53 ` [Fastboot] " Magnus Damm
2006-08-22 9:25 ` Eric W. Biederman
2006-08-23 3:10 ` Magnus Damm
2006-08-22 9:01 ` Andi Kleen
2006-08-22 9:20 ` Eric W. Biederman
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=20060821144657.GE9549@in.ibm.com \
--to=vgoyal@in.ibm.com \
--cc=ak@suse.de \
--cc=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=magnus@valinux.co.jp \
/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