qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] trace: drop orphan events from ./trace-events
Date: Tue, 23 Sep 2014 11:11:12 +0100	[thread overview]
Message-ID: <20140923101112.GK2713@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <87vbof64ms.fsf@blackfin.pond.sub.org>

[-- Attachment #1: Type: text/plain, Size: 4136 bytes --]

On Mon, Sep 22, 2014 at 05:45:15PM +0200, Markus Armbruster wrote:
> Stefan Hajnoczi <stefanha@redhat.com> writes:
> 
> > 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.
> 
> Reviewed-by: Markus Armbruster <armbru@redhat.com>
> 
> While you're at it, could you also clean up the pointers to source files
> that have bit-rotted?

Sure, please post a separate patch with your Signed-off-by and I'll
merge it.

Stefan

> $ scripts/cleanup-trace-events.pl trace-events | diff -u trace-events -
> --- trace-events	2014-09-22 17:40:04.228700732 +0200
> +++ -	2014-09-22 17:41:03.107310697 +0200
> @@ -836,7 +836,7 @@
>  pvscsi_tx_rings_ppn(const char* label, uint64_t ppn) "%s page: %"PRIx64""
>  pvscsi_tx_rings_num_pages(const char* label, uint32_t num) "Number of %s pages: %u"
>  
> -# xen-all.c
> +# xen-hvm.c
>  xen_ram_alloc(unsigned long ram_addr, unsigned long size) "requested: %#lx, size %#lx"
>  xen_client_set_memory(uint64_t start_addr, unsigned long size, bool log_dirty) "%#"PRIx64" size %#lx, log_dirty %i"
>  
> @@ -845,7 +845,7 @@
>  xen_remap_bucket(uint64_t index) "index %#"PRIx64
>  xen_map_cache_return(void* ptr) "%p"
>  
> -# hw/xen/xen_platform.c
> +# hw/i386/xen/xen_platform.c
>  xen_platform_log(char *s) "xen platform: %s"
>  
>  # qemu-coroutine.c
> @@ -1075,6 +1075,7 @@
>  vmware_scratch_write(uint32_t index, uint32_t value) "index %d, value 0x%x"
>  vmware_setmode(uint32_t w, uint32_t h, uint32_t bpp) "%dx%d @ %d bpp"
>  
> +# vmstate.c
>  # savevm.c
>  savevm_section_start(const char *id, unsigned int section_id) "%s, section_id %u"
>  savevm_section_end(const char *id, unsigned int section_id) "%s, section_id %u"
> @@ -1241,7 +1242,7 @@
>  virtio_ccw_interpret_ccw(int cssid, int ssid, int schid, int cmd_code) "VIRTIO-CCW: %x.%x.%04x: interpret command %x"
>  virtio_ccw_new_device(int cssid, int ssid, int schid, int devno, const char *devno_mode) "VIRTIO-CCW: add subchannel %x.%x.%04x, devno %04x (%s)"
>  
> -# hw/intc/s390_flic.c
> +# hw/intc/s390_flic_kvm.c
>  flic_create_device(int err) "flic: create device failed %d"
>  flic_no_device_api(int err) "flic: no Device Contral API support %d"
>  flic_reset_failed(int err) "flic: reset failed %d"
> @@ -1254,6 +1255,7 @@
>  migrate_pending(uint64_t size, uint64_t max) "pending size %" PRIu64 " max %" PRIu64
>  migrate_transferred(uint64_t tranferred, uint64_t time_spent, double bandwidth, uint64_t size) "transferred %" PRIu64 " time_spent %" PRIu64 " bandwidth %g max_size %" PRId64
>  
> +# target-ppc/kvm.c
>  # kvm-all.c
>  kvm_ioctl(int type, void *arg) "type 0x%x, arg %p"
>  kvm_vm_ioctl(int type, void *arg) "type 0x%x, arg %p"
> @@ -1282,10 +1284,12 @@
>  object_dynamic_cast_assert(const char *type, const char *target, const char *file, int line, const char *func) "%s->%s (%s:%d:%s)"
>  object_class_dynamic_cast_assert(const char *type, const char *target, const char *file, int line, const char *func) "%s->%s (%s:%d:%s)"
>  
> -# hw/xen/xen_pvdevice.c
> +# hw/i386/xen/xen_pvdevice.c
>  xen_pv_mmio_read(uint64_t addr) "WARNING: read from Xen PV Device MMIO space (address %"PRIx64")"
>  xen_pv_mmio_write(uint64_t addr) "WARNING: write to Xen PV Device MMIO space (address %"PRIx64")"
>  
> +# hw/i386/pc.c
> +# hw/acpi/memory_hotplug.c
>  # hw/pci/pci_host.c
>  pci_cfg_read(const char *dev, unsigned devid, unsigned fnid, unsigned offs, unsigned val) "%s %02u:%u @0x%x -> 0x%x"
>  pci_cfg_write(const char *dev, unsigned devid, unsigned fnid, unsigned offs, unsigned val) "%s %02u:%u @0x%x <- 0x%x"

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-09-23 10:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 14:03 [Qemu-devel] [PATCH 0/3] trace: drop orphan events from ./trace-events Stefan Hajnoczi
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 [this message]
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=20140923101112.GK2713@stefanha-thinkpad.redhat.com \
    --to=stefanha@redhat.com \
    --cc=armbru@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).