netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: netdev@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	mst@redhat.com
Subject: [PATCH 0/2] adding tracepoints to vhost
Date: Tue, 10 Apr 2012 10:58:10 +0800	[thread overview]
Message-ID: <20120410025327.49693.93562.stgit@amd-6168-8-1.englab.nay.redhat.com> (raw)

To help in vhost analyzing, the following series adding basic tracepoints to
vhost. Operations of both virtqueues and vhost works were traced in current
implementation, net code were untouched. A top-like satistics displaying script
were introduced to help the troubleshooting.

TODO:
- net specific tracepoints?

---

Jason Wang (2):
      vhost: basic tracepoints
      tools: virtio: add a top-like utility for displaying vhost satistics


 drivers/vhost/trace.h   |  153 ++++++++++++++++++++
 drivers/vhost/vhost.c   |   17 ++
 tools/virtio/vhost_stat |  360 +++++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 528 insertions(+), 2 deletions(-)
 create mode 100644 drivers/vhost/trace.h
 create mode 100755 tools/virtio/vhost_stat

-- 
Jason Wang

             reply	other threads:[~2012-04-10  2:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10  2:58 Jason Wang [this message]
2012-04-10  2:58 ` [PATCH 1/2] vhost: basic tracepoints Jason Wang
2012-05-07 21:10   ` Michael S. Tsirkin
2012-04-10  2:58 ` [PATCH 2/2] tools: virtio: add a top-like utility for displaying vhost satistics Jason Wang
2012-04-10 11:40 ` [PATCH 0/2] adding tracepoints to vhost Stefan Hajnoczi
2012-04-10 12:42   ` Michael S. Tsirkin
2012-04-10 12:54     ` Stefan Hajnoczi
2012-04-10 13:10     ` Zhi Yong Wu
2012-04-10 13:45       ` Michael S. Tsirkin
2012-04-10 14:58         ` Zhi Yong Wu

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=20120410025327.49693.93562.stgit@amd-6168-8-1.englab.nay.redhat.com \
    --to=jasowang@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.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).