public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Billy Rose <billyrose@cox-internet.com>
To: krishnakumar@naturesoft.net, Tim Bird <tim.bird@am.sony.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel mode console
Date: Thu, 4 Mar 2004 18:58:45 -0600	[thread overview]
Message-ID: <200403041858.45617.billyrose@cox-internet.com> (raw)
In-Reply-To: <200403040942.23176.krishnakumar@naturesoft.net>

On Wednesday 03 March 2004 10:12 pm, Krishnakumar. R wrote:
> Hi,
>
> > set up a remote debug session just to poke around in the kernel.
> > Remote debug setup is complex and often fragile.
>
> There is framework called "Kprobes" available, which may
> be of use in the cases were remote debugging is a no-no.
>
> After you have applied the kprobes patch, you can put probes
> at different portions of the kernel and can dump registers
> variables etc.
>
> More details can be found at
> http://www-124.ibm.com/linux/projects/kprobes.
>
>
> Regards,
> KK.

i think perhaps i need to expound upon what i have a vision of. a kernel mode 
console is just that: a console designed to run in kernel mode. it could have 
built in commands to allow for quick and dirty examination of stuff (anything 
really, like memory dumps) and a command processor for scripted stuff, but 
the true power of it comes in when you issue a command that is not internal 
to the console. it could run a special debugger, an application that installs 
a probe, a memory monitor, etc., etc. in short it is not a debugger per-say, 
but a "god mode" console for the linux kernel. that is what i had a vision 
of. the executables it would run would necessarily be compiled for that. 
again, i ask is that worth the time coding it?
-- 
. ~billyrose/make

  reply	other threads:[~2004-03-05  1:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03  3:52 kernel mode console Billy Rose
2004-03-03  3:57 ` H. Peter Anvin
2004-03-03 17:09   ` Matt Mackall
2004-03-03 16:49 ` Tim Bird
2004-03-04  4:12   ` Krishnakumar. R
2004-03-05  0:58     ` Billy Rose [this message]
2004-03-05  3:20       ` Rob Couto
2004-03-05 11:47       ` John Bradford
     [not found] <200403022152.06950.billyrose@cox-internet.com.suse.lists.linux.kernel>
2004-03-03 17:18 ` Andi Kleen

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=200403041858.45617.billyrose@cox-internet.com \
    --to=billyrose@cox-internet.com \
    --cc=krishnakumar@naturesoft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim.bird@am.sony.com \
    /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