All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dor Laor <dlaor@redhat.com>
To: qemu-devel@nongnu.org
Cc: Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] Eliminate references to	logfile/loglevel global vars
Date: Sat, 13 Dec 2008 00:27:39 +0200	[thread overview]
Message-ID: <4942E55B.6080507@redhat.com> (raw)
In-Reply-To: <1229117060-8467-1-git-send-email-ehabkost@redhat.com>

Eduardo Habkost wrote:
> Hi,
>
> This is actually a long 63-patch series, but for a first request for comments,
> I am splitting it in two parts:
>
> 1) A set of macros are introduced for almost all usage patterns of the
>    logfile/loglevel global variables.
> 2) 62 patches that convert almost all references to the logfile/loglevel
>    global variables to use those macros (the PATCH 1/2 e-mail actually
>    has pointers to the patches, either as small individual patches,
>    or as a big single patch file).
>
> These macros are _not_ a proposal for a definitive new logging API. They
> are just a step for it: a way to group all usage patterns of the
> logfile/loglevel variables on a single place. After all usage of those
> variables is eliminated, we can more easily refactor the code to have
> a proper logging API.
>
> This series needs my previous debugging-#ifdef cleanup series to be applied
> before it.
>
> It shouldn't change any qemu behavior, but just move all references
> to the logging global variables to a single place, keeping exactly the
> same behaviour.
>
>   
It is a blessed addition.

What about providing configure option to enable all the debug #ifdef?
Once we have it, we can set the debug level using the monitor for all debug
targets. For kvm is shouldn't introduce a measurable overhead since
it mostly uses the device model. It will be also ease debugging qemu
when there is no clue about the root cause it hard to predict at compile 
time.

We can have something like ./configure --full-debug
and #ifdef (FULL_DEBUG || DEBUG_IO_PORTS) for example.

      parent reply	other threads:[~2008-12-12 22:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-12 21:24 [Qemu-devel] [RFC PATCH 0/2] Eliminate references to logfile/loglevel global vars Eduardo Habkost
2008-12-12 21:24 ` [Qemu-devel] [RFC PATCH 1/2] Create macros that will help define the logging API Eduardo Habkost
2008-12-12 21:24 ` [Qemu-devel] [RFC PATCH URL 2/2] Big conversion to the new logging macros Eduardo Habkost
2008-12-12 21:30   ` Anthony Liguori
2008-12-12 21:52     ` Blue Swirl
2008-12-12 22:27 ` Dor Laor [this message]

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=4942E55B.6080507@redhat.com \
    --to=dlaor@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=qemu-devel@nongnu.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.