* [RFC] Cleaning up SCM debug
@ 2005-06-23 3:20 Anthony Liguori
2005-06-23 9:44 ` Keir Fraser
0 siblings, 1 reply; 2+ messages in thread
From: Anthony Liguori @ 2005-06-23 3:20 UTC (permalink / raw)
To: xen-devel, xense-devel
Hi,
public/acm.h defines both an ACM_DEBUG flag and a printkd function that,
if ACM_DEBUG is defined will convert to a printk. public/acm.h is
included by userspace applications where printk isn't necessarily
meaningful. Furthermore, it appears ACM_DEBUG is only used within Xen
anyway so making it apart of the public headers doesn't make much sense.
Therefore, I'd like to move ACM_DEBUG and printkd into acm/acm_core.h.
While at it, it seems like a good idea to change the printkd into either
one of the existing Xen debug macros or to get rid of it altogether.
I wanted to check first to see if there was an emerging standard macro
(a quick glance shows printk, DPRINTK, PRINT, and I'm sure there are at
least a few more). Recommendations are appreciated.
Regards,
Anthony Liguori
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [RFC] Cleaning up SCM debug
2005-06-23 3:20 [RFC] Cleaning up SCM debug Anthony Liguori
@ 2005-06-23 9:44 ` Keir Fraser
0 siblings, 0 replies; 2+ messages in thread
From: Keir Fraser @ 2005-06-23 9:44 UTC (permalink / raw)
To: Anthony Liguori; +Cc: xen-devel, xense-devel
On 23 Jun 2005, at 04:20, Anthony Liguori wrote:
> public/acm.h defines both an ACM_DEBUG flag and a printkd function
> that, if ACM_DEBUG is defined will convert to a printk. public/acm.h
> is included by userspace applications where printk isn't necessarily
> meaningful. Furthermore, it appears ACM_DEBUG is only used within Xen
> anyway so making it apart of the public headers doesn't make much
> sense.
>
> Therefore, I'd like to move ACM_DEBUG and printkd into acm/acm_core.h.
> While at it, it seems like a good idea to change the printkd into
> either one of the existing Xen debug macros or to get rid of it
> altogether.
>
> I wanted to check first to see if there was an emerging standard macro
> (a quick glance shows printk, DPRINTK, PRINT, and I'm sure there are
> at least a few more). Recommendations are appreciated.
If they are debug printk's then they should map onto DPRINTK. The PRINT
macro is specific to debugging within the SEDF scheduler.
-- Keir
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-06-23 9:44 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-06-23 3:20 [RFC] Cleaning up SCM debug Anthony Liguori
2005-06-23 9:44 ` Keir Fraser
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.