Re: driver debugging and logging Re: logging using printk, klogd

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jun 10, 2004 at 19:25:27 +0530, aksingh@hss.hns.com wrote:
>   Had a general question -- do driver writers log there messages, because
> it is a massive performance hit, do they have printk's in their code when
> they release it ?
>   It is certainly desirable to have something of this sort(atleast some
> messages being logged), incase there is some problem with the
> driver(detected in field) then the logs can really help .

Users have the source. It's easy to:

#ifdef DEBUG
#define LOG(x...) printk(x)
#else
#define LOG(x) 0
#endif

And when a problem arises, the user can always be told to #define DEBUG
and recompile the module. Right?

-------------------------------------------------------------------------------
						 Jan 'Bulb' Hudec <bulb@ucw.cz>

Attachment: signature.asc
Description: Digital signature


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux