From: George Anzinger <george@mvista.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: "Amit S. Kale" <amitkale@emsyssoft.com>,
Pavel Machek <pavel@ucw.cz>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
kgdb-bugreport@lists.sourceforge.net
Subject: Re: [Kgdb-bugreport] [PATCH] Kill kgdb_serial
Date: Thu, 11 Mar 2004 14:53:34 -0800 [thread overview]
Message-ID: <4050EDEE.6050706@mvista.com> (raw)
In-Reply-To: <20040311223321.GL5169@smtp.west.cox.net>
Tom Rini wrote:
> On Thu, Mar 11, 2004 at 01:33:40PM -0800, George Anzinger wrote:
>
>
>>Tom Rini wrote:
>>
>>
>>>>I am afraid I don't quite understand what he was saying other than early
>>>>init stuff. On of the problems with trying early init stuff, by the way,
>>>>is that a lot of things depend on having alloc up and that happens rather
>>>>late in the game.
>>>
>>>
>>>I assume you aren't talking about kgdb stuff here (or what would be the
>>>point of going so early) but I believe he was talking about allowing for
>>>stuff that could be done early, to be done early.
>>
>>One of the issues with the UART set up is registering the interrupt handler
>>with the kernel. It will fail if alloc is not up. The -mm patch does two
>>things with this. a) It tries every getchar to register the interrupt
>>handler, and b) it has a module init entry to register it. This last will
>>happen late in the bring up and is safe. a) is there to get it ASAP if you
>>are actually using kgdb during the bring up.
>
>
> There's two ways to look at this.
> - All the more reason to acknowledge that the earliest you can safely
> get into KGDB is point X, where X is where alloc works,
Just to get ^C to work? I would rather give it up entirely!
mappings done
> if needed, etc, etc, and IFF we change things slightly in kgdboe so
> that it can call kgdb_schedule_breakpoint() if it needs to as an
> initial break, and handle setting kgdb_serial to the serial driver in
> kgdb_arch_init, or something, and remove all of the extra kludges to
> get us a few lines / function calls earlier on.
> - More and more special cases.
How about a command line set up ASAP which calls a driver entry to do the break.
The driver being serial does it NOW, but being some thing that needs
additional resources, just sets a flag to break when it gets them and returns.
Seems rather simple.
>
> Roughly. :)
>
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2004-03-11 22:54 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 21:39 [PATCH] Kill kgdb_serial Tom Rini
2004-03-02 22:02 ` [Kgdb-bugreport] " George Anzinger
2004-03-02 22:11 ` Tom Rini
2004-03-02 22:31 ` Pavel Machek
2004-03-02 22:41 ` Tom Rini
2004-03-02 23:00 ` Tom Rini
2004-03-02 23:35 ` Pavel Machek
2004-03-03 15:22 ` Tom Rini
2004-03-03 15:51 ` Pavel Machek
2004-03-03 16:04 ` Tom Rini
2004-03-04 0:34 ` George Anzinger
2004-03-04 5:01 ` Amit S. Kale
2004-03-04 22:02 ` George Anzinger
2004-03-04 22:48 ` Tom Rini
2004-03-02 23:46 ` George Anzinger
2004-03-02 23:52 ` Tom Rini
2004-03-03 0:36 ` George Anzinger
2004-03-03 15:20 ` Tom Rini
2004-03-04 0:30 ` George Anzinger
2004-03-03 5:43 ` Amit S. Kale
2004-03-03 15:16 ` Tom Rini
2004-03-04 0:27 ` George Anzinger
2004-03-04 15:17 ` Tom Rini
2004-03-04 22:18 ` George Anzinger
2004-03-04 22:49 ` Tom Rini
2004-03-04 4:41 ` Amit S. Kale
2004-03-04 15:27 ` Tom Rini
2004-03-04 23:06 ` George Anzinger
2004-03-04 23:17 ` Tom Rini
2004-03-11 21:33 ` George Anzinger
2004-03-11 22:33 ` Tom Rini
2004-03-11 22:53 ` George Anzinger [this message]
2004-03-11 23:00 ` Tom Rini
2004-03-11 23:46 ` George Anzinger
2004-03-12 4:52 ` Amit S. Kale
2004-03-12 4:48 ` Amit S. Kale
2004-03-03 15:26 ` Matt Mackall
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=4050EDEE.6050706@mvista.com \
--to=george@mvista.com \
--cc=amitkale@emsyssoft.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=trini@kernel.crashing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox