From: Tom Rini <trini@kernel.crashing.org>
To: Andi Kleen <ak@suse.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, amitkale@linsyssoft.com
Subject: Re: [patch 07/15] Basic x86_64 support
Date: Thu, 4 Aug 2005 12:08:47 -0700 [thread overview]
Message-ID: <20050804190847.GF3337@smtp.west.cox.net> (raw)
In-Reply-To: <20050804185632.GD8266@wotan.suse.de>
On Thu, Aug 04, 2005 at 08:56:32PM +0200, Andi Kleen wrote:
> On Thu, Aug 04, 2005 at 08:06:36AM -0700, Tom Rini wrote:
> > >
> > > Why can't you run on x86-64 early?
> >
> > As I said earlier:
> > "
> > > If you want to run gdb earlier you need to do it without a tasklet.
> >
> > We really would like to try again once stacks are setup (IOW, once
> > if ((&__get_cpu_var(init_tss))[0].ist[0])) is true).
> > "
> >
> > IOW, when we parse the params on x86_64 this isn't true (or rather it
> > wasn't true as of 2.6.9'ish, if this has changed I'd be glad to retest
> > things).
>
> The ISTs are set up for the boot processor extremly early - even
> before start_kernel. But they are useless before trap_init()
> runs because you won't get any exceptions that need an IDT (or rather
> they will all still point to the early exception handler that just panics)
I wonder if there was a reason we couldn't do what we did with i386 and
make an early_trap_init() so that we can get what we care about that
early at least. I'll have to poke at this a bit more, thanks!
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2005-08-04 19:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1.2972005.trini@kernel.crashing.org>
2005-07-29 21:18 ` [patch 01/15] KGDB: Core files Tom Rini
2005-07-29 21:18 ` [patch 02/15] KGDB: i386 core functionality Tom Rini
2005-07-29 21:19 ` [patch 03/15] Basic PowerPC32 support Tom Rini
2005-07-29 21:19 ` [patch 04/15] I/O driver for 8250-compatible UARTs Tom Rini
2005-07-29 21:19 ` [patch 05/15] Basic MIPS support Tom Rini
2005-07-29 21:19 ` [patch 06/15] Basic IA64 support Tom Rini
2005-07-29 21:20 ` [patch 07/15] Basic x86_64 support Tom Rini
2005-07-29 21:20 ` [patch 08/15] Basic SuperH support Tom Rini
2005-07-29 21:20 ` [patch 09/15] KGDB: Basic ARM support Tom Rini
2005-07-29 21:20 ` [patch 10/15] Basic support for PowerPC64 Tom Rini
2005-07-29 21:20 ` [patch 11/15] KGDB: KGDBoE I/O driver Tom Rini
2005-07-29 21:21 ` [patch 12/15] KGDB: Add CFI DWARF2 annotation support Tom Rini
2005-07-29 21:21 ` [patch 13/15] Minor SysRq keyboard bugfix for KGDB Tom Rini
2005-07-29 21:21 ` [patch 14/15] Allow KGDB to work well with loaded modules Tom Rini
2005-07-29 21:21 ` [patch 15/15] Add hardware breakpoint support for i386 Tom Rini
2005-08-04 0:55 ` [patch 11/15] KGDB: KGDBoE I/O driver Matt Mackall
2005-08-03 13:05 ` [patch 07/15] Basic x86_64 support Andi Kleen
2005-08-03 13:37 ` Tom Rini
2005-08-04 12:39 ` Andi Kleen
2005-08-04 14:04 ` Tom Rini
2005-08-04 14:06 ` Andi Kleen
2005-08-04 14:14 ` Tom Rini
2005-08-04 14:28 ` Andi Kleen
2005-08-04 15:06 ` Tom Rini
2005-08-04 18:56 ` Andi Kleen
2005-08-04 19:08 ` Tom Rini [this message]
2005-08-07 0:48 ` Keith Owens
2005-08-08 17:56 ` Tom Rini
2005-08-01 10:19 ` [patch 05/15] Basic MIPS support Ralf Baechle
2005-08-01 10:24 ` Christoph Hellwig
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=20050804190847.GF3337@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=amitkale@linsyssoft.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.