From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>, l@dorileo.org
Subject: [Qemu-devel] [PATCH v3 4/9] qemu-log: Avoid function call for disabled qemu_log_mask logging
Date: Thu, 31 Jul 2014 14:06:27 +0100 [thread overview]
Message-ID: <1406811992-6766-5-git-send-email-alex.bennee@linaro.org> (raw)
In-Reply-To: <1406811992-6766-1-git-send-email-alex.bennee@linaro.org>
From: Peter Maydell <peter.maydell@linaro.org>
Make qemu_log_mask() a macro which only calls the function to
do the actual work if the logging is enabled. This avoids making
a function call in possible fast paths where logging is disabled.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
diff --git a/include/qemu/log.h b/include/qemu/log.h
index d515424..da22e13 100644
--- a/include/qemu/log.h
+++ b/include/qemu/log.h
@@ -64,10 +64,17 @@ qemu_log_vprintf(const char *fmt, va_list va)
}
}
-/* log only if a bit is set on the current loglevel mask
+/* log only if a bit is set on the current loglevel mask:
+ * @mask: bit to check in the mask
+ * @fmt: printf-style format string
+ * @args: optional arguments for format string
*/
-void GCC_FMT_ATTR(2, 3) qemu_log_mask(int mask, const char *fmt, ...);
-
+#define qemu_log_mask(MASK, FMT, ...) \
+ do { \
+ if (unlikely(qemu_loglevel_mask(MASK))) { \
+ qemu_log(FMT, ## __VA_ARGS__); \
+ } \
+ } while (0)
/* Special cases: */
diff --git a/qemu-log.c b/qemu-log.c
index 35bbb56..83e0cb4 100644
--- a/qemu-log.c
+++ b/qemu-log.c
@@ -36,17 +36,6 @@ void qemu_log(const char *fmt, ...)
va_end(ap);
}
-void qemu_log_mask(int mask, const char *fmt, ...)
-{
- va_list ap;
-
- va_start(ap, fmt);
- if ((qemu_loglevel & mask) && qemu_logfile) {
- vfprintf(qemu_logfile, fmt, ap);
- }
- va_end(ap);
-}
-
/* enable or disable low levels log */
void do_qemu_set_log(int log_flags, bool use_own_buffers)
{
--
2.0.3
next prev parent reply other threads:[~2014-07-31 13:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 13:06 [Qemu-devel] [PATCH v3 0/9] qemu-log dfilter and perf.map changes Alex Bennée
2014-07-31 13:06 ` [Qemu-devel] [PATCH v3 1/9] tcg: add ability to dump /tmp/perf-<pid>.map files Alex Bennée
2014-07-31 13:06 ` [Qemu-devel] [PATCH v3 2/9] tcg: light re-factor and pass down TranslationBlock Alex Bennée
2014-07-31 13:06 ` [Qemu-devel] [PATCH v3 3/9] qemu-log: correct help text for -d cpu Alex Bennée
2014-08-11 11:12 ` Andreas Färber
2014-07-31 13:06 ` Alex Bennée [this message]
2014-08-11 11:14 ` [Qemu-devel] [PATCH v3 4/9] qemu-log: Avoid function call for disabled qemu_log_mask logging Andreas Färber
2014-07-31 13:06 ` [Qemu-devel] [PATCH v3 5/9] qemu-log: Improve the "exec" TB execution logging Alex Bennée
2014-07-31 13:06 ` [Qemu-devel] [PATCH v3 6/9] qemu-log: support simple pid substitution in logfile Alex Bennée
2014-07-31 13:06 ` [Qemu-devel] [PATCH v3 7/9] qemu-log: new option -dfilter to limit output Alex Bennée
2014-07-31 13:06 ` [Qemu-devel] [PATCH v3 8/9] qemu-log: dfilter-ise exec, out_asm, and op_opt Alex Bennée
2014-07-31 13:06 ` [Qemu-devel] [PATCH v3 9/9] target-arm: dfilter support for in_asm, op, opt_op Alex Bennée
2014-08-11 9:37 ` [Qemu-devel] [PATCH v3 0/9] qemu-log dfilter and perf.map changes Alex Bennée
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=1406811992-6766-5-git-send-email-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=l@dorileo.org \
--cc=peter.maydell@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).