From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: stefanha@redhat.com
Subject: Re: [PATCH 4/4] trace-events: Fix attribution of trace points to source
Date: Thu, 6 Aug 2020 16:54:57 +0200 [thread overview]
Message-ID: <792eea2f-0e73-0b02-9c0d-81e2b5fad249@redhat.com> (raw)
In-Reply-To: <20200806141334.3646302-5-armbru@redhat.com>
On 8/6/20 4:13 PM, Markus Armbruster wrote:
> Some trace points are attributed to the wrong source file. Happens
> when we neglect to update trace-events for code motion, or add events
> in the wrong place, or misspell the file name.
>
> Clean up with help of scripts/cleanup-trace-events.pl. Funnies
> requiring manual post-processing:
>
> * accel/tcg/cputlb.c trace points are in trace-events.
>
> * block.c and blockdev.c trace points are in block/trace-events.
>
> * hw/block/nvme.c uses the preprocessor to hide its trace point use
> from cleanup-trace-events.pl.
>
> * hw/tpm/tpm_spapr.c uses pseudo trace point tpm_spapr_show_buffer to
> guard debug code.
>
> * include/hw/xen/xen_common.h trace points are in hw/xen/trace-events.
>
> * linux-user/trace-events abbreviates a tedious list of filenames to
> */signal.c.
>
> * net/colo-compare and net/filter-rewriter.c use pseudo trace points
> colo_compare_miscompare and colo_filter_rewriter_debug to guard
> debug code.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> block/trace-events | 5 ++---
> hw/block/trace-events | 2 +-
> hw/char/trace-events | 2 +-
> hw/display/trace-events | 4 +++-
> hw/hyperv/trace-events | 2 +-
> hw/mips/trace-events | 2 +-
> hw/misc/trace-events | 8 +++++---
> hw/ppc/trace-events | 6 ++----
> hw/riscv/trace-events | 2 +-
> hw/rtc/trace-events | 2 +-
> hw/tpm/trace-events | 2 +-
> hw/usb/trace-events | 4 +++-
> hw/vfio/trace-events | 10 ++++++----
> hw/virtio/trace-events | 2 +-
> migration/trace-events | 36 +++++++++++++++++++-----------------
> target/riscv/trace-events | 2 +-
> trace-events | 5 +++--
> ui/trace-events | 6 +++---
> util/trace-events | 4 +++-
> 19 files changed, 58 insertions(+), 48 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2020-08-06 14:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 14:13 [PATCH 0/4] trace-events: Clean up Markus Armbruster
2020-08-06 14:13 ` [PATCH 1/4] scripts/cleanup-trace-events: Fix for vcpu property Markus Armbruster
2020-08-06 14:13 ` [PATCH 2/4] scripts/cleanup-trace-events: Emit files in alphabetical order Markus Armbruster
2020-08-06 14:13 ` [PATCH 3/4] trace-events: Delete unused trace points Markus Armbruster
2020-08-06 14:13 ` [PATCH 4/4] trace-events: Fix attribution of trace points to source Markus Armbruster
2020-08-06 14:54 ` Philippe Mathieu-Daudé [this message]
2020-08-12 19:29 ` [PATCH 0/4] trace-events: Clean up Stefan Hajnoczi
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=792eea2f-0e73-0b02-9c0d-81e2b5fad249@redhat.com \
--to=philmd@redhat.com \
--cc=armbru@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).