On Tue, Apr 10, 2012 at 3:58 AM, Jason Wang jasow...@redhat.com 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
On Tue, Apr 10, 2012 at 12:40:50PM +0100, Stefan Hajnoczi wrote:
On Tue, Apr 10, 2012 at 3:58 AM, Jason Wang jasow...@redhat.com 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
On Tue, Apr 10, 2012 at 1:42 PM, Michael S. Tsirkin m...@redhat.com 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 jasow...@redhat.com wrote:
To help in vhost analyzing, the following series adding basic tracepoints
to
On Tue, Apr 10, 2012 at 8:42 PM, Michael S. Tsirkin m...@redhat.com 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 jasow...@redhat.com wrote:
To help in vhost analyzing, the following series adding basic tracepoints
to
On Tue, Apr 10, 2012 at 09:10:48PM +0800, Zhi Yong Wu wrote:
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
On Tue, Apr 10, 2012 at 9:45 PM, Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Apr 10, 2012 at 09:10:48PM +0800, Zhi Yong Wu wrote:
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
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
