From: Avi Kivity <avi@qumranet.com>
To: "Liu, Eric E" <eric.e.liu@intel.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: [PATCH RFC 0/4]Porting Xentrace to kvm
Date: Sun, 16 Mar 2008 17:28:59 +0200 [thread overview]
Message-ID: <47DD3CBB.9050201@qumranet.com> (raw)
In-Reply-To: <9D7649D18729DE4BB2BD7B494F7FEDC201084D2D@pdsmsx415.ccr.corp.intel.com>
Liu, Eric E wrote:
> Hi,
> The following patches port xentrace to kvm which is useful for
> performance tuning and debugging.
>
> It is designed to allow debugging traces of kvm to be generated on
> Up/Smp machines. Each trace entry is outputted in a trace ring buffer
> for per cpu which is mapped to userspace, and the userspace tools can
> analyze the data according to some formats definitions.
>
> Since we already have had debugfs_entries and some other kernel debug
> mechanism to use, does this kvmtrace make sense? Any comment is
> welcomed.
>
This looks very useful. While kvm_stat provides good data, this is much
more in depth.
The kernel already contains a method of transferring percpu data to
userspace; see Documentation/filesystems/relay.txt. It supports mmap()
and read(). Please see if it is a good fit.
Please post patches with individual subjects, instead of having the same
subject for every patch.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-03-16 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 5:13 [PATCH RFC 0/4]Porting Xentrace to kvm Liu, Eric E
2008-03-16 15:28 ` Avi Kivity [this message]
2008-03-16 15:45 ` Jan Kiszka
2008-03-16 15:53 ` Avi Kivity
2008-03-16 16:12 ` Jan Kiszka
2008-03-17 9:20 ` Liu, Eric E
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=47DD3CBB.9050201@qumranet.com \
--to=avi@qumranet.com \
--cc=eric.e.liu@intel.com \
--cc=kvm-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.