kdb
[Top] [All Lists]

Re: [PATCH] KDB for ppc64 - write to OF stdout instead of console

To: linas@xxxxxxxxxxxxxx
Subject: Re: [PATCH] KDB for ppc64 - write to OF stdout instead of console
From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
Date: Fri, 21 May 2004 14:52:01 +0200
Cc: kdb@xxxxxxxxxxx, ananth@xxxxxxxxxx, vosburgh@xxxxxxxxxx, anton@xxxxxxxxx, linuxppc64-dev@xxxxxxxxxxxxxxxxxx, olof@xxxxxxxxxxxxxx
In-reply-to: <20040519120219.B39874@forte.austin.ibm.com>
References: <20040518140754.GA19828@in.ibm.com> <ECB0E186-A992-11D8-85E9-000A95A4DC02@kernel.crashing.org> <20040519120219.B39874@forte.austin.ibm.com>
Sender: kdb-bounce@xxxxxxxxxxx
On 19-mei-04, at 19:02, linas@xxxxxxxxxxxxxx wrote:
> On Wed, May 19, 2004 at 02:49:10PM +0200, Segher Boessenkool wrote:
>>> Patch inlined removes KDB's dependency on consoles completely for 
>>> I/O.
>>> With this patch, we use the OF stdout for both input and output.
>>
>> OF stdout is not necessarily the same thing as OF stdin
>> (and, in fact, very often isn't) -- please use stdin for
>> input?
>
> The problem was actually with output, not input.  People were seeing
> the KDB prompt on the serial console, and so they would assume they
> had input, when in fact they didn't.  And so this insane dance would
> start, "KDB is hung, @#$%^& KDB".

I didn't read the actual patch, just the description.  And that
set off some alarms here ;-)

I guess what the patch actually does is "use OF stdout for output,
and OF stdin for input", which is fine fine fine.


Segher

---------------------------
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
<Prev in Thread] Current Thread [Next in Thread>