From: Jason Wang <jasowang@redhat.com>
To: mst@redhat.com, kvm@vger.kernel.org,
virtio-dev@lists.oasis-open.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Jason Wang <jasowang@redhat.com>
Subject: [PATCH RFC V2 1/4] vhost: introduce queue_index for tracing
Date: Fri, 21 Mar 2014 17:41:50 +0800 [thread overview]
Message-ID: <1395394913-19548-2-git-send-email-jasowang@redhat.com> (raw)
In-Reply-To: <1395394913-19548-1-git-send-email-jasowang@redhat.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
---
drivers/vhost/net.c | 1 +
drivers/vhost/vhost.h | 3 +++
2 files changed, 4 insertions(+)
diff --git a/drivers/vhost/net.c b/drivers/vhost/net.c
index a0fa5de..85d666c 100644
--- a/drivers/vhost/net.c
+++ b/drivers/vhost/net.c
@@ -708,6 +708,7 @@ static int vhost_net_open(struct inode *inode, struct file *f)
n->vqs[i].done_idx = 0;
n->vqs[i].vhost_hlen = 0;
n->vqs[i].sock_hlen = 0;
+ n->vqs[i].vq.queue_index = i;
}
vhost_dev_init(dev, vqs, VHOST_NET_VQ_MAX);
diff --git a/drivers/vhost/vhost.h b/drivers/vhost/vhost.h
index 35eeb2a..6e36416 100644
--- a/drivers/vhost/vhost.h
+++ b/drivers/vhost/vhost.h
@@ -96,6 +96,9 @@ struct vhost_virtqueue {
/* Last used index value we have signalled on */
bool signalled_used_valid;
+ /* Queue index used for tracing */
+ u16 queue_index;
+
/* Log writes to used structure. */
bool log_used;
u64 log_addr;
--
1.8.3.2
next prev parent reply other threads:[~2014-03-21 9:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 9:41 [PATCH RFC V2 0/4] Adding tracepoints to vhost/net Jason Wang
2014-03-21 9:41 ` Jason Wang [this message]
2014-03-21 9:41 ` [PATCH RFC V2 2/4] vhost: basic tracepoints Jason Wang
2014-03-21 9:41 ` [PATCH RFC V2 3/4] vhost_net: add basic tracepoints for vhost_net Jason Wang
2014-03-21 9:41 ` [PATCH RFC V2 4/4] tools: virtio: add a top-like utility for displaying vhost satistics Jason Wang
2014-04-10 9:27 ` Fam Zheng
2014-04-11 3:04 ` Jason Wang
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=1395394913-19548-2-git-send-email-jasowang@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=virtio-dev@lists.oasis-open.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).