From: Gerd Hoffmann <kraxel@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] hw/audio/sb16.c: Convert file to new logging API
Date: Thu, 1 Feb 2018 09:17:11 +0100 [thread overview]
Message-ID: <20180201081711.vu3ou7mdwww365j2@sirius.home.kraxel.org> (raw)
In-Reply-To: <BCDC8A8F-F8CE-4F71-A11C-CF7078FB6BAF@gmail.com>
> > ldebug() should probably trace points.
>
> I need help with this. I tried replacing ldebug() with
> "qemu_log_mask(LOG_TRACE,", but that caused a lot of messages to be
> printed to the terminal. It is odd because I thought I had to use "-d
> trace" to make it print. Do you have another suggestion on what to
> replace ldebug() with?
See docs/devel/tracing.txt
You might also have a look at commit
6aa22a29187e1908f5db738d27c64a9efc8d0bfa as example (adds some trace
points to vnc code).
HTH,
Gerd
prev parent reply other threads:[~2018-02-01 8:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 5:18 [Qemu-devel] [PATCH] hw/audio/sb16.c: Convert file to new logging API John Arbuckle
2018-01-30 9:41 ` Gerd Hoffmann
2018-01-30 15:30 ` Programmingkid
2018-01-31 9:22 ` Gerd Hoffmann
2018-01-31 21:43 ` Programmingkid
2018-01-31 22:18 ` Programmingkid
2018-02-01 8:17 ` Gerd Hoffmann [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=20180201081711.vu3ou7mdwww365j2@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=programmingkidx@gmail.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 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).