From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Sanghyun Hong <shhong@umd.edu>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Alina Nicolae <alinanicolae992@gmail.com>
Subject: Re: Questions about Using Perf at Dom0
Date: Mon, 29 Aug 2016 12:36:20 -0400 [thread overview]
Message-ID: <f912c9f6-bee9-31ea-e76b-c65ae5be9047@oracle.com> (raw)
In-Reply-To: <EC3E0D5F-0A43-4BE7-A940-5E14A9339D02@umd.edu>
On 08/29/2016 09:18 AM, Sanghyun Hong wrote:
> Dear Xen-Devel Community:
>
> I’m a grad student working on measuring performance counters at the
> Xen domains. I read this
> thread(https://wiki.xenproject.org/wiki/Xen_Profiling:_oprofile_and_perf) in
> web, and it says using Linux perf command will let us collecting
> performance counters in both dom0 and domU. Does it mean that we can
> collect both of them at once if we run perf command on the dom0? (If
> not, does it mean we can collect counters for each domain separately
> once we run the perf command in each domain?
Profiling both guest and dom0 (and the hypervisor) requires changes to
perf and those are not there yet.
But you can run perf in each guest (including dom0) separately. Make
sure you have vpmu=true boot option.
-boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-08-29 16:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 13:18 Questions about Using Perf at Dom0 Sanghyun Hong
2016-08-29 16:36 ` Boris Ostrovsky [this message]
2016-08-29 18:42 ` Sanghyun Hong
2016-08-29 20:59 ` Boris Ostrovsky
2016-08-29 21:08 ` Sanghyun Hong
2016-08-29 21:24 ` Boris Ostrovsky
2016-08-29 21:48 ` Sanghyun Hong
2016-08-29 22:37 ` Boris Ostrovsky
2016-08-30 0:12 ` Sanghyun Hong
2016-08-30 14:39 ` Boris Ostrovsky
2016-08-30 15:22 ` Sanghyun Hong
2016-08-30 16:05 ` Boris Ostrovsky
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=f912c9f6-bee9-31ea-e76b-c65ae5be9047@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=alinanicolae992@gmail.com \
--cc=shhong@umd.edu \
--cc=xen-devel@lists.xen.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).