On Tue, Apr 10, 2012 at 1:42 PM, Michael S. Tsirkin <mst@xxxxxxxxxx> wrote: > On Tue, Apr 10, 2012 at 12:40:50PM +0100, Stefan Hajnoczi wrote: >> On Tue, Apr 10, 2012 at 3:58 AM, Jason Wang <jasowang@xxxxxxxxxx> wrote: >> > 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 >> >> Perhaps this can replace the vhost log feature? I'm not sure if >> tracepoints support the right data types but it seems like vhost >> debugging could be done using tracing with less code. >> >> Stefan > > vhost log is not a debugging tool, it logs memory accesses for > migration. Thanks. I totally misunderstood its purpose. Stefan -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
