Re: remote debugging via FireWire * __fast__ firedump!

2007-12-06 Thread Bernhard Kaindl
On Tue, 4 Dec 2007, Stefan Richter wrote: A quick note to this text from http://www.suse.de/~bk/firewire/ohci1394_dma_early.diff : + As all changes to the FireWire bus such as enabling and disabling + devices cause a bus reset and thereby disable remote DMA for all + dev

Re: remote debugging via FireWire * __fast__ firedump!

2007-12-06 Thread Bernhard Kaindl
On Tue, 4 Dec 2007, Andi Kleen wrote: I have just had the guts to explore __fast__ memory dumping over firewire for full-system dumps [...] Unfortunately it won't work for >3GB or so AFAIK. Yes we seem to be limited to 4GB mostly, with 3G mem hole, it's 3GB. Afterwards, the victim was dea

Re: remote debugging via FireWire * __fast__ firedump!

2007-12-04 Thread Stefan Richter
PPS: Today I had a brief look through your current sources. Look good so far, except for a curious hunk which patches drivers/Makefile. And I can't say anything to the x86 platform related and PCI related aspects of the driver. -- Stefan Richter -=-=-=== ==-- --=-- http://arcgraph.de/sr/ --

Re: remote debugging via FireWire * __fast__ firedump!

2007-12-04 Thread Stefan Richter
Stefan Richter wrote: > Bernhard Kaindl wrote: >> The biggest block size that worked here was 2048 bytes, which was >> enough to get nearly 10MB/s of data transfer rate from the remote >> memory to disk. > > The maximum payload size of block requests depends on three things: > 1. speed of the conn

Re: remote debugging via FireWire * __fast__ firedump!

2007-12-04 Thread Stefan Richter
Bernhard Kaindl wrote: > The biggest block size that worked here was 2048 bytes, which was > enough to get nearly 10MB/s of data transfer rate from the remote > memory to disk. The maximum payload size of block requests depends on three things: 1. speed of the connection between the two nodes (deb

Re: remote debugging via FireWire * __fast__ firedump!

2007-12-04 Thread Andi Kleen
On Tuesday 04 December 2007 04:45:22 am Bernhard Kaindl wrote: > I just wanted to let you know that I'll have picked up the early > firewire patch again and cleaned it up very much so that it should > be ready to submit it and but it on the patch-submission road. Nice. > I have just had the g

Re: remote debugging via FireWire * __fast__ firedump!

2007-12-03 Thread Bernhard Kaindl
Hi, I just wanted to let you know that I'll have picked up the early firewire patch again and cleaned it up very much so that it should be ready to submit it and but it on the patch-submission road. What's left to do is to write some HOWTO like Stefan describes below, but I'll try to get that

Re: remote debugging via FireWire

2007-02-11 Thread Benjamin Herrenschmidt
On Mon, 2007-02-12 at 07:49 +0100, Andi Kleen wrote: > On Sunday 11 February 2007 22:35, Benjamin Herrenschmidt wrote: > > > I'd like to have that on ppc as well, so I'd rather keep it in drivers/ > > This will need some abstraction at least -- there are some early mapping hacks > that are x86 sp

Re: remote debugging via FireWire

2007-02-11 Thread Andi Kleen
On Sunday 11 February 2007 22:35, Benjamin Herrenschmidt wrote: > I'd like to have that on ppc as well, so I'd rather keep it in drivers/ This will need some abstraction at least -- there are some early mapping hacks that are x86 specific right now. > I agree that it doesn't need to be a module.

Re: remote debugging via FireWire

2007-02-11 Thread Benjamin Herrenschmidt
On Sat, 2007-02-10 at 20:16 +0100, Stefan Richter wrote: > [ohci1394_early] > > Some remarks to the September 2006 version at > http://www.suse.de/~bk/firewire/ : > > - Seems its .remove won't work properly if more than one OHCI-1394 > controller is installed. And it's .probe isn't reentra

Re: remote debugging via FireWire

2007-02-10 Thread Stefan Richter
[ohci1394_early] Some remarks to the September 2006 version at http://www.suse.de/~bk/firewire/ : - Seems its .remove won't work properly if more than one OHCI-1394 controller is installed. And it's .probe isn't reentrant, but that might be less of a problem. - Its functionality will

Re: remote debugging via FireWire

2007-02-10 Thread Andi Kleen
On Saturday 10 February 2007 16:14, Stefan Richter wrote: > Andi Kleen wrote: > > On Saturday 10 February 2007 14:51, Stefan Richter wrote: > >> Could be handled via linux1394-2.6.git, although a > >> different channel where the actual users of this facility watch would > >> IMO be more appropriate

Re: remote debugging via FireWire

2007-02-10 Thread Stefan Richter
Andi Kleen wrote: > On Saturday 10 February 2007 14:51, Stefan Richter wrote: >> Could be handled via linux1394-2.6.git, although a >> different channel where the actual users of this facility watch would >> IMO be more appropriate. > > It's more related to arch code than firewire, so I thought i

Re: remote debugging via FireWire (was What will be in the x86-64/x86 2.6.21 merge)

2007-02-10 Thread Andi Kleen
On Saturday 10 February 2007 14:51, Stefan Richter wrote: > Andi Kleen wrote at LKML: > ... > > Not likely to make .21: > ... > > - Early firewire support for firescope at early boot > ... > > Was it seen in canonical patch format on a mailinglist before? Don't know. > Is it Bernhard Kaindl's oh

remote debugging via FireWire (was What will be in the x86-64/x86 2.6.21 merge)

2007-02-10 Thread Stefan Richter
Andi Kleen wrote at LKML: ... > Not likely to make .21: ... > - Early firewire support for firescope at early boot ... Was it seen in canonical patch format on a mailinglist before? Is it Bernhard Kaindl's ohci1394_early? http://www.suse.de/~bk/firewire/ Would be good to put this on the usual pat