From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH 0/3] trace: drop orphan events from ./trace-events
Date: Mon, 22 Sep 2014 15:03:12 +0100 [thread overview]
Message-ID: <1411394595-15300-1-git-send-email-stefanha@redhat.com> (raw)
Over time a few unused trace events have been left behind in ./trace-events.
Either the code that called them was deleted or the event was never called in
the first place.
This is a clear violation of the solider's motto "no man left behind". It's
time to bring these trace events home.
On a more serious note, unused trace events cause confusion to users who want
to enable existing instrumentation. On the SystemTap backend we get errors
when attempting to enable them because the static probes that these events are
based on do not exist.
Stefan Hajnoczi (3):
trace-events: drop orphan virtio_blk_data_plane_complete_request
trace-events: drop orphan usb_mtp_data_out
trace-events: drop orphan iscsi trace events
block/iscsi.c | 1 -
trace-events | 8 --------
2 files changed, 9 deletions(-)
--
1.9.3
next reply other threads:[~2014-09-22 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 14:03 Stefan Hajnoczi [this message]
2014-09-22 14:03 ` [Qemu-devel] [PATCH 1/3] trace-events: drop orphan virtio_blk_data_plane_complete_request Stefan Hajnoczi
2014-09-22 14:03 ` [Qemu-devel] [PATCH 2/3] trace-events: drop orphan usb_mtp_data_out Stefan Hajnoczi
2014-09-22 14:03 ` [Qemu-devel] [PATCH 3/3] trace-events: drop orphan iscsi trace events Stefan Hajnoczi
2014-09-22 15:45 ` [Qemu-devel] [PATCH 0/3] trace: drop orphan events from ./trace-events Markus Armbruster
2014-09-23 10:11 ` Stefan Hajnoczi
2014-09-23 12:53 ` Markus Armbruster
2014-09-24 13:38 ` 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=1411394595-15300-1-git-send-email-stefanha@redhat.com \
--to=stefanha@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 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).