public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Pavel Machek <pavel@ucw.cz>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	kgdb-bugreport@lists.sourceforge.net,
	"Amit S. Kale" <amitkale@emsyssoft.com>
Subject: Re: [Kgdb-bugreport] [PATCH] Kill kgdb_serial
Date: Wed, 03 Mar 2004 16:30:33 -0800	[thread overview]
Message-ID: <404678A9.4070709@mvista.com> (raw)
In-Reply-To: <20040303152020.GR20227@smtp.west.cox.net>

Tom Rini wrote:
> On Tue, Mar 02, 2004 at 04:36:11PM -0800, George Anzinger wrote:
> 
>>Tom Rini wrote:
>>
>>>Regardless, it's not that we offer (nor does the -mm version, from what
>>>I read of it) eth or serial at any point, it simply allows for serial to
>>>be used and a switchover to eth.  And if kgdb is attached at the time,
>>>it's a 'fun' gdb session (or at least is was when I was trying it out in
>>>-mm and then in my own version).
>>
>>I am not really suggesting a live switch capability, more like something 
>>that is set a boot time.
> 
> 
> That's still not, AFAICT, what's offered in -mm or kgdb.sf.net.
> 
> 
>>>The real problem is that you start getting quite complex when you allow
>>>for a system to be kgdb eth, or 8250, or some arch serial driver, or
>>>some other I/O driver, and so on.  PPC has 3, and I don't see it getting
>>>smaller from there.
>>
>>I had imagined that it would be rather like a file system.  The stub would 
>>pass (or it could be a global if you prefer) the index to use into an array 
>>of interface structures.  Something like:
>>
>>struct kgdb_interface {
>>	void (*kgdb_in)(*char)
>>	:
>>	:
>>}
>>
>>struct kgdb_interface kgdb_io_array[N];
> 
> 
> And how do you pick a default?

A config option.
> 
> 
>>>And with both of those points, I don't think it's worth the trouble that
>>>point 2 is, given the limitations of point 1.
>>
>>I imagine that I would like this.  I would use the eth interface until 
>>required to use the serial.  I would rather not have to rebuild the kernel 
>>to do this....
> 
> 
> Then you're talking about live switching again, or some sort of control
> from userland.
> 

No, I would still choose this at boot time, it is just that I have to reboot the 
same kernel, not a new one.  It would be frozen once kgdb sees the command line. 
  Prior to that it would be the default chosen at config time.

-- 
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


  reply	other threads:[~2004-03-04  0:32 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 [this message]
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
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=404678A9.4070709@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