mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>, <linux-trace-users@vger.kernel.org>
Cc: John Kacur <jkacur@redhat.com>
Subject: [ANNOUNCE] trace-cmd 2.5.2 (and others)
Date: Thu, 5 Feb 2015 17:32:37 -0500	[thread overview]
Message-ID: <20150205173237.673691d0@gandalf.local.home> (raw)


You can get trace-cmd from:

  https://git.kernel.org/cgit/linux/kernel/git/rostedt/trace-cmd.git/


Tag: trace-cmd-v2.5.2

trace-cmd: Version 2.5.2

Changes since Version 2.5.1:

 o Added support for tracefs filesystem.

 o profile: Show timestamps of max and mins

 o profile: Add -H for user specified event hooking

 o Have -H in record be saved for report --profile to use

 o Save uname in trace.dat.

 o Cleanups

 o Fixes

-------------------------------------------------------

Tag: trace-cmd-v2.4.1

trace-cmd: Version 2.4.1

Changes since Version 2.4.0:

 o Add support for tracefs file system

 o Add support for IP address formats

 o Handle %z in bprint format

 o Several fixes

 o Some clean ups

-------------------------------------------------------

Tag: trace-cmd-v2.3.3

trace-cmd: Version 2.3.3

Changes since v2.3.2:

 o Added support for tracefs file system

 o Add support for IP address formats

 o Handle '%z' in bprint format

 o Print event name when showing warings (if possible)

 o Have recording to instances not affect top level buffer

 o Have trace-on reset for existing instances

 o Show better error messages on bad function args

 o Several fixes

 o Clean ups

-------------------------------------------------------

Tag: trace-cmd-v2.2.3

trace-cmd: Version 2.2.3

Changes since Version 2.2.2:

 o Add support for tracefs file system

 o Add support for IP address formats

 o Handle '%z' in bprint format

 o Add scsi_plugin

 o Add xen_plugin

 o Add cfg80211 plugin

 o Print event names on warning (if possible)

 o Report better error messages on bad function args

 o Handle __print_hex(__get_dynamic_array(fieldname))

 o Add "make dist" target

 o Have bprintk output the same as the kernel does

 o Several fixes

 o Several clean ups

-------------------------------------------------------

Tag: trace-cmd-v2.1.5

trace-cmd: Version 2.1.5

Changes since Version 2.1.4:

 o Add support for tracefs file system

 o Add support for IP address formats

 o Handle '%z' in bprint format

 o Add scsi_plugin

 o Add xen plugin

 o Add cfg80211 plugin

 o Handle __print_hex(__get_dynamic_array(fieldname), len)

 o Print event name whan showing warnings (if possible)

 o Report better error messages on bad function args

 o Report unknown VMX exit reasons with code

 o Add a "make dist" target

 o Update VMX exit reasons in KVM plugin

 o Several fixes

 o Several clean ups

NOTE: trace-cmd 2.1 series has now entered End-of-life. No more updates
will be done to this branch.

All series before 2.1 have already entered End-of-life and are no
longer supported.

-- Steve

             reply	other threads:[~2015-02-05 22:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-05 22:32 Steven Rostedt [this message]
2015-02-06 14:35 ` Steven Rostedt

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=20150205173237.673691d0@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=jkacur@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-users@vger.kernel.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

all inboxes | Powered by JetHome®