linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Bernhard Kaindl <bk@suse.de>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
	Andi Kleen <ak@suse.de>, Bernhard Kaindl <bkaindl@ffii.org>,
	linux-kernel@vger.kernel.org,
	linux1394-devel@lists.sourceforge.net,
	Thomas Renninger <trenn@suse.de>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] Early boot debugging via FireWire (ohci1394_dma=early)
Date: Mon, 17 Dec 2007 14:49:30 +0100	[thread overview]
Message-ID: <20071217134929.GJ1870@elte.hu> (raw)
In-Reply-To: <alpine.LNX.0.9999-openSUSE-1.0712061936370.21849@jbgna.fhfr.qr>


* Bernhard Kaindl <bk@suse.de> wrote:

> Subject of this patch:
> 
> This patch adds a new configuration option, which adds support for a 
> new early_param which gets checked in 
> arch/x86/kernel/setup_{32,64}.c:setup_arch() to decide wether 
> OHCI-1394 FireWire controllers should be initialized and enabled for 
> physical DMA access to allow remote debugging of early problems like 
> issues ACPI or other subsystems which are executed very early.
> 
> If the config option is not enabled, no code is changed, and if the 
> boot paramenter is not given, no new code is executed, and independent 
> of that, all new code is freed after boot, so the config option can be 
> even enabled in standard, non-debug kernels.
> 
> With specialized tools, it is then possible to get debugging 
> information from machines which have no serial ports (notebooks) such 
> as the printk buffer contents, or any data which can be referenced 
> from global pointers, if it is stored below the 4GB limit and even 
> memory dumps of of the physical RAM region below the 4GB limit can be 
> taken without any cooperation from the CPU of the host, so the machine 
> can be crashed early, it does not matter.

cool stuff! I've tentatively added your patch to x86.git (pending more 
review feedback from others), but it already looks quite nice to me.

	Ingo

  parent reply	other threads:[~2007-12-17 13:50 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-10 11:42 What will be in the x86-64/x86 2.6.21 merge Andi Kleen
2007-02-10 13:43 ` [discuss] " Muli Ben-Yehuda
2007-02-10 13:52   ` Andi Kleen
2007-02-10 13:56     ` Muli Ben-Yehuda
2007-02-10 14:03       ` Andi Kleen
2007-02-10 13:51 ` remote debugging via FireWire (was What will be in the x86-64/x86 2.6.21 merge) Stefan Richter
2007-02-10 14:02   ` Andi Kleen
2007-02-10 15:14     ` remote debugging via FireWire Stefan Richter
2007-02-10 15:41       ` Andi Kleen
2007-02-10 19:16         ` Stefan Richter
2007-02-11 21:35           ` Benjamin Herrenschmidt
2007-02-12  6:49             ` Andi Kleen
2007-02-12  7:29               ` Benjamin Herrenschmidt
2007-12-04  3:45   ` remote debugging via FireWire * __fast__ firedump! Bernhard Kaindl
2007-12-04  7:39     ` Andi Kleen
2007-12-06 16:02       ` Bernhard Kaindl
2007-12-04 22:15     ` Stefan Richter
2007-12-04 22:34       ` Stefan Richter
2007-12-04 22:40         ` Stefan Richter
2007-12-06 18:36           ` [feedback discussion] Early boot debugging via FireWire (ohci1394_dma=early) Bernhard Kaindl
2007-12-06 19:23             ` Stefan Richter
2007-12-06 19:23             ` [PATCH] " Bernhard Kaindl
2007-12-06 20:23               ` Stefan Richter
2007-12-17 13:49               ` Ingo Molnar [this message]
2007-12-06 16:32       ` remote debugging via FireWire * __fast__ firedump! Bernhard Kaindl
2007-02-12 14:11 ` What will be in the x86-64/x86 2.6.21 merge James Morris
2007-02-12 14:14   ` Andi Kleen
2007-02-12 14:46     ` James Morris
2007-02-14  6:53     ` Rusty Russell

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=20071217134929.GJ1870@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=bk@suse.de \
    --cc=bkaindl@ffii.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=tglx@linutronix.de \
    --cc=trenn@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).