mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Jun Koi <junkoi2004@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Firewire debugging tools - firedump & fireproxy?
Date: Thu, 30 Jul 2009 18:37:22 +0300	[thread overview]
Message-ID: <1248968242.3624.28.camel@maxim-laptop> (raw)
In-Reply-To: <87k51qfqve.fsf@basil.nowhere.org>

On Thu, 2009-07-30 at 11:43 +0200, Andi Kleen wrote:
> Jun Koi <junkoi2004@gmail.com> writes:
> 
> > Hi,
> >
> > I am doing some debugging via firewire. I found some references to
> > some tools named firedump & fireproxy, made by Bernhard Kaindl,
> > supposed put at following addresses:
> >
> > ftp://ftp.suse.de/private/bk/firewire/tools/firedump-0.1.tar.bz2
> > ftp://ftp.suse.de/private/bk/firewire/tools/fireproxy-0.33.tar.bz2
> 
> I have a copy of Bernd's website on http://halobates.de/firewire
> 
> firescope is also on my servers (I did the original x86 version)
> 
> -Andi
> 
>  

Thanks a lot.
Don't know what to say about what I could do to help...
I could help to make this tool better, don't know how much time will
permit me, or at least I think that kgdbom can be merged almost as is
already.
As it stands from the source, it just creates a ring buffer in memory
for commands as if there were send over gdb. Dead simple it seems.
Thus, fireproxy could be reduced (if it isn't...) to simple "read string
from memory over firewire and hand over to gdb via tcp and vise versa.
This should give back all power kgdb has for free (currently fireproxy
states that only very basic support is implemented)

Could some of you put these tools on kernel.org?
Debugging over firewire seems to be the best of the best.


BTW, it is almost always possible to take over the CPU even without help
of kgdbom (if system got in state even it doesn't work)
Say CPU is in protected mode, and you know where the IDT lives.
You could program some device to trigger an IRQ (HPET seems to be the
best), set up the APIC to route it, and then trigger, and now the CPU
should enter the IRQ handler. (Of course this needs that firewire device
be able to access HPET and IOAPIC which are nowadays located on
southbridge)

And probably the only device that can't be debugged, is the firewire
driver itself that is standard compliant, and well tested...

Best regards,
	Maxim Levitsky


  reply	other threads:[~2009-07-30 15:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-05  5:42 Jun Koi
2009-07-30  5:36 ` Maxim Levitsky
2009-07-30  7:01   ` Jun Koi
2009-07-30  8:31   ` Jason Wessel
2009-07-30 20:57     ` Maxim Levitsky
2009-07-30 21:10       ` Jason Wessel
2009-07-31  4:55         ` Maxim Levitsky
2009-07-30  9:43 ` Andi Kleen
2009-07-30 15:37   ` Maxim Levitsky [this message]
2009-07-30 15:49     ` 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=1248968242.3624.28.camel@maxim-laptop \
    --to=maximlevitsky@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=junkoi2004@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®