From: "Michael S. Tsirkin" <mst@redhat.com>
To: Zhi Yong Wu <zwu.kernel@gmail.com>
Cc: virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 0/2] adding tracepoints to vhost
Date: Tue, 10 Apr 2012 16:45:22 +0300 [thread overview]
Message-ID: <20120410134522.GC18899@redhat.com> (raw)
In-Reply-To: <CAEH94Li0==w=AUKd5WCPMcqxLh=+N6bKttOwrE8y-xuOyPt_QA@mail.gmail.com>
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 tool, it logs memory accesses for
> > migration.
> Great, it is very appreciated if there's some docs about this
About what? vhost logging? See the comment near the
definition of VHOST_SET_LOG_BASE in vhost.h
> > _______________________________________________
> > Virtualization mailing list
> > Virtualization@lists.linux-foundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/virtualization
>
>
>
> --
> Regards,
>
> Zhi Yong Wu
next prev parent reply other threads:[~2012-04-10 13:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 2:58 [PATCH 0/2] adding tracepoints to vhost Jason Wang
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 [this message]
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=20120410134522.GC18899@redhat.com \
--to=mst@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=zwu.kernel@gmail.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;
as well as URLs for NNTP newsgroup(s).