Re: IOLog on serial port? Or to use kprintf?
Re: IOLog on serial port? Or to use kprintf?
- Subject: Re: IOLog on serial port? Or to use kprintf?
- From: Justin Walker <email@hidden>
- Date: Sat, 22 Jan 2005 12:22:58 -0800
Following up on my own post:
On Jan 21, 2005, at 18:03, Justin Walker wrote:
On Jan 21, 2005, at 16:00, Parav Pandit wrote:
Hi,
Currently I see my IOLog() messages in to the
/var/log/system.log file.
[snip]
FYI, if you do succeed in getting kprintf output directed to a serial
port (cf. mail from Markus and Felix in this thread), be aware that
using it will noticeably degrade the performance of your system (the
last I looked, kprintf() uses polling to output to its device, and for
serial, that means "forever" with interrupts disabled).
The last time I used kprintf to serial posts (when I was young, and
there was Rhapsody in the air), it degraded the performance of the
ethernet driver/network stack by about 90% (I was debugging the stack).
Regards,
Justin
--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics | It's not whether you win or
lose...
| It's whether *I* win or lose.
*--------------------------------------*-------------------------------*
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden