On Sat, Feb 10, 2007 at 01:31:20PM +0100, Blaisorblade wrote:
> libc's printf has an enormous stack usage, so that my_printf is used for
> direct output instead of printf; if this is ok because it's bootup
> code,
It is bootup code only.
> then *fatal* should be marked as "bootup code only";
OK.
> otherwise
> we may reuse vsprintf() and write() or fputs(); this should match
> what happens in my_printf, to avoid any unlikely problem with libc's
> buffering.
Offhand, I would say that if we are on a kernel stack, printk is safe
to use, and should be used, so there's no need for things like
my_printf. Maybe there are some exceptions in early boot when the
kernel is running, but before the console is working, but I can't
think of any problems we've had like that.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
