LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: kgdb-bugreport@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: kgdb 2.6.28 merge plans
Date: Wed, 22 Oct 2008 13:25:30 +0100	[thread overview]
Message-ID: <20081022132530.0c6bc859@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <48FEFB65.3090902@windriver.com>

> This is a discussion that needs to be hashed out.  It is a question of
> where would you like it discussed (IE: new thread in lmkl,
> linux-serial@...)?

Either of those. I'd also love to drive the sysrq hook out of every
driver in the process. It seems the sysrq key, and debugger activation
are all the same thing.

> It is a discussion more about general polled vs interrupt driven
> serial/tty APIs, not all of which are used for debuggers.  I am open
> to help fix/change/extend/refactor the existing kernel's CONSOLE_POLL
> API or even deprecate it in favor of something else so long as it
> leads to an interface which can allow the sharing of the hardware
> among various contexts with early_printk, console, tty, debugger,
> etc...

What I've done so far is begin to create a "tty_port" object, the idea
being that every tty device will eventually contain one which exists for
the lifetime of the hardware object and have enough methods for printk
console (and now for polled input)

> If it was all obvious and easy, it would have already been done.  Rome
> was not built in a day after all. :-)

Agreed entirely - and in this case we have to convert a twisty maze of
ad-hoc building into Rome without breaking it during the rennovations

I certainly was not expecting a quick follow up patch to fix all these
problems, rather that it gets tackled in an orderly manner for 2.6.29/30
somewhere.

Alan

      reply	other threads:[~2008-10-22 12:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-21 19:14 Jason Wessel
2008-10-21 19:14 ` [PATCH 1/7] kgdb: Add the ability to schedule a breakpoint via a tasklet Jason Wessel
2008-10-21 19:14   ` [PATCH 2/7] tty: Fix sparse static warning for tty_driver_lookup_tty Jason Wessel
2008-10-21 19:14     ` [PATCH 3/7] kgdboc, tty: Add the rx polling call back capability Jason Wessel
2008-10-21 19:14       ` [PATCH 4/7] kgdboc, 8250: Add the rx polling hook to 8250 driver Jason Wessel
2008-10-21 19:14         ` [PATCH 5/7] kgdboc, tty: use tty open to start low level drivers Jason Wessel
2008-10-21 19:14           ` [PATCH 6/7] kgdb: kgdboc console poll hooks for serial_txx9 uart Jason Wessel
2008-10-21 19:14             ` [PATCH 7/7] kgdb: Make mem access function weak in kgdb.c andkgdb.h Jason Wessel
2008-10-21 21:49           ` [PATCH 5/7] kgdboc, tty: use tty open to start low level drivers Jason Wessel
2008-10-21 22:47           ` Alan Cox
2008-10-22  1:54             ` Jason Wessel
2008-10-21 22:49 ` kgdb 2.6.28 merge plans Alan Cox
2008-10-22  2:09   ` Jason Wessel
2008-10-22  8:34     ` Alan Cox
2008-10-22 10:07       ` Jason Wessel
2008-10-22 12:25         ` Alan Cox [this message]

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=20081022132530.0c6bc859@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=jason.wessel@windriver.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: kgdb 2.6.28 merge plans' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).