From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>
Subject: [PATCH v2 0/4] [RfC] fix tracing for modules
Date: Tue, 24 Nov 2020 17:02:51 +0100 [thread overview]
Message-ID: <20201124160255.28111-1-kraxel@redhat.com> (raw)
First version that actually works. Only qxl covered for this RfC, other
modules will follow once the basics are hashed out.
More context:
https://bugzilla.redhat.com/show_bug.cgi?id=1898700
https://bugzilla.redhat.com/show_bug.cgi?id=1869642
take care,
Gerd
Gerd Hoffmann (4):
meson: add trace_events_config[]
meson: move up hw subdir (specifically before trace subdir)
meson: add module_trace & module_trace_src
meson: move qxl trace events to separate file
hw/display/qxl-render.c | 1 +
hw/display/qxl.c | 1 +
hw/display/meson.build | 5 +++
hw/display/trace-events | 67 -------------------------------------
hw/display/trace-events-qxl | 66 ++++++++++++++++++++++++++++++++++++
meson.build | 7 ++--
trace/meson.build | 37 +++++++++++++++-----
7 files changed, 106 insertions(+), 78 deletions(-)
create mode 100644 hw/display/trace-events-qxl
--
2.27.0
next reply other threads:[~2020-11-24 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 16:02 Gerd Hoffmann [this message]
2020-11-24 16:02 ` [PATCH v2 1/4] meson: add trace_events_config[] Gerd Hoffmann
2020-11-24 16:02 ` [PATCH v2 2/4] meson: move up hw subdir (specifically before trace subdir) Gerd Hoffmann
2020-11-24 16:02 ` [PATCH v2 3/4] meson: add module_trace & module_trace_src Gerd Hoffmann
2020-11-24 16:02 ` [PATCH v2 4/4] meson: move qxl trace events to separate file Gerd Hoffmann
2020-11-30 16:56 ` [PATCH v2 0/4] [RfC] fix tracing for modules Stefan Hajnoczi
2020-12-03 10:39 ` Gerd Hoffmann
2020-12-15 16:36 ` Gerd Hoffmann
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=20201124160255.28111-1-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).