>
> [ i've already sent this mail today, but nothing delivered. ]
> [ sorry, if both received ]
>
> Hello,
>
[clipped]
> then before every (needed) printks ktrans_mng() will be called.
>
> init/main.c_956:
> ktrans_mng(KTRANS_CODE, KTR_CALIB);
> printk("Calibrating delay loop... ");
>
> init/main.c_1119:
> ktrans_mng(KTRANS_CODE, KTR_BANNER);
> printk(linux_banner);
What will happen on an SMP machine, if they both try to printk
something? Either you'll need a lock, or you'll need to keep track of
which CPU that printk belonged to. I understand your intent, but
perhaps we need to provide a cleaner logging facility.
I see the benefit of arbitrary printk's during development. It turns
out that many things that are useful during development, turn out to be
also useful in a production environment. So now you need to change
your mindset to think about internationalization while all you want to
do is debug your driver? Very hard to do. We need to make it easier
for the developer as well as beneficial for the international user.
The signal/noise ratio seems to be good, but is there enough interest
for this to start a new list? Sorry, I can't offer any resources
(behind a firewall, you know).
Drago
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/