public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Raspl <raspl@linux.vnet.ibm.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, rkrcmar@redhat.com, frankja@linux.vnet.ibm.com
Subject: [PATCH v2 00/11] tools/kvm_stat: misc fixes
Date: Mon, 11 Dec 2017 12:25:18 +0100	[thread overview]
Message-ID: <20171211112529.33706-1-raspl@linux.vnet.ibm.com> (raw)

Fixed a few more glitches, most of which should be pretty straight forward.
I'm not happy with what the man page looks like, in that the "INTERACTIVE
COMMANDS" section's line width is way too small. I noticed this in
particular with 5/11 "tools/kvm_stat: fix child trace events accounting",
but couldn't find a way to get ASCIIDOC to widen those lines a bit.


Stefan Raspl (11):
  tools/kvm_stat: fix command line option '-g'
  tools/kvm_stat: fix drilldown in events-by-guests mode
  tools/kvm_stat: fix missing field update after filter change
  tools/kvm_stat: fix extra handling of 'help' with fields filter
  tools/kvm_stat: fix child trace events accounting
  tools/kvm_stat: add hint on '-f help' to man page
  tools/kvm_stat: handle invalid regular expressions
  tools/kvm_stat: suppress usage information on command line errors
  tools/kvm_stat: stop ignoring unhandled arguments
  tools/kvm_stat: sort '-f help' output
  tools/kvm_stat: add line for totals

 tools/kvm/kvm_stat/kvm_stat     | 76 ++++++++++++++++++++++++-----------------
 tools/kvm/kvm_stat/kvm_stat.txt |  4 ++-
 2 files changed, 48 insertions(+), 32 deletions(-)

-- 
2.13.5

             reply	other threads:[~2017-12-11 11:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-11 11:25 Stefan Raspl [this message]
2017-12-11 11:25 ` [PATCH v2 01/11] tools/kvm_stat: fix command line option '-g' Stefan Raspl
2017-12-11 11:25 ` [PATCH v2 02/11] tools/kvm_stat: fix drilldown in events-by-guests mode Stefan Raspl
2017-12-11 11:25 ` [PATCH v2 03/11] tools/kvm_stat: fix missing field update after filter change Stefan Raspl
2017-12-11 11:25 ` [PATCH v2 04/11] tools/kvm_stat: fix extra handling of 'help' with fields filter Stefan Raspl
2017-12-11 11:25 ` [PATCH v2 05/11] tools/kvm_stat: fix child trace events accounting Stefan Raspl
2017-12-11 11:25 ` [PATCH v2 06/11] tools/kvm_stat: add hint on '-f help' to man page Stefan Raspl
2017-12-11 11:25 ` [PATCH v2 07/11] tools/kvm_stat: handle invalid regular expressions Stefan Raspl
2017-12-11 11:25 ` [PATCH v2 08/11] tools/kvm_stat: suppress usage information on command line errors Stefan Raspl
2017-12-12 15:53   ` Paolo Bonzini
2017-12-12 18:09     ` Stefan Raspl
2017-12-11 11:25 ` [PATCH v2 09/11] tools/kvm_stat: stop ignoring unhandled arguments Stefan Raspl
2017-12-12 15:56   ` Paolo Bonzini
2017-12-12 18:04     ` Stefan Raspl
2017-12-12 18:06       ` Paolo Bonzini
2017-12-11 11:25 ` [PATCH v2 10/11] tools/kvm_stat: sort '-f help' output Stefan Raspl
2017-12-11 12:20   ` Janosch Frank
2017-12-12 11:30     ` Stefan Raspl
2017-12-12 13:59     ` Stefan Raspl
2017-12-12 18:21     ` Stefan Raspl
2017-12-11 11:25 ` [PATCH v2 11/11] tools/kvm_stat: add line for totals Stefan Raspl
2017-12-12 16:00 ` [PATCH v2 00/11] tools/kvm_stat: misc fixes Paolo Bonzini

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=20171211112529.33706-1-raspl@linux.vnet.ibm.com \
    --to=raspl@linux.vnet.ibm.com \
    --cc=frankja@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@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