All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: dprintk() and gdprintk() to be compiled out when NDEBUG
Date: Wed, 11 Feb 2015 10:34:02 +0000	[thread overview]
Message-ID: <54DB301A.9090206@citrix.com> (raw)
In-Reply-To: <54DB3DE0020000780005EF1D@mail.emea.novell.com>

On 11/02/15 10:32, Jan Beulich wrote:
>>>> On 11.02.15 at 11:05, <andrew.cooper3@citrix.com> wrote:
>> On 11/02/15 07:50, Jan Beulich wrote:
>>> I'd like to propose to honor the 'd' in these functions' names (which
>>> I understand to mean "debug") in that such functions should be
>>> no-ops in non-debug builds. I'd then be inclined to introduce a
>>> gprintk() automatically adding XENLOG_GUEST and the printing of
>>> current using the %pv format. Quite likely the (mis-)use of these
>>> two functions may then temporarily result in messages not meant
>>> to be debugging ones to become hidden in non-debug builds. If
>>> others agree, I'd try to make one pass through the tree to try to
>>> identify such, but I'd like to ask others to also keep an eye on that
>>> aspect.
>> I agree.  I suspect many of the existing gdprintk()s will need to turn
>> into dprintk()s.
> Maybe, but that's yet another topic (unless you meant gprintk()s
> instead of dprintk()s).

I did mean gprintk().  Sorry.

~Andrew

  reply	other threads:[~2015-02-11 10:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11  7:50 dprintk() and gdprintk() to be compiled out when NDEBUG Jan Beulich
2015-02-11 10:05 ` Andrew Cooper
2015-02-11 10:32   ` Jan Beulich
2015-02-11 10:34     ` Andrew Cooper [this message]
2015-02-18 10:58 ` Ian Campbell
2015-02-18 11:05   ` Jan Beulich
2015-02-18 11:40     ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54DB301A.9090206@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.