From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Vince Weaver <vincent.weaver-e7X0jjDqjFGHXe+LvDLADg@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Peter Zijlstra <peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
Paul Mackerras <paulus-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>,
Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Arnaldo Carvalho de Melo
<acme-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Gleb Natapov <gleb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Subject: Re: [patch] perf_event_open.2 exclude_host/exclude_guest clarification
Date: Tue, 06 Jan 2015 07:45:34 +0100 [thread overview]
Message-ID: <54AB848E.2080808@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1412051027470.10310-6xBS8L8d439fDsnSvq7Uqyn2WXadKZNJe7X0jjDqjFGHXe+LvDLADg@public.gmane.org>
Hi Vince et al,
On 12/05/2014 04:41 PM, Vince Weaver wrote:
> Hello
>
> The PAPI developers recently ran into some issues with the various virtual
> machine related settings in the perf_event_open() system call.
>
> What follows is what my proposed updated manpage sections look like; I'm
> hoping to get some sort of feedback about the correctness of these statements.
Vince, thanks for the proposed patches.
Does anyone have feedback about the correctness of Vince's proposed patches?
>
> exclude_hv
> If this bit is set, the count excludes events that happen in
> the hypervisor. This is mainly for PMUs that have
> built-in hardware support for this feature (such as POWER;
> this setting is silently ignored on x86).
>
> ...
>
> exclude_host (since Linux 3.2)
> When conducting measurements that include processes
> running VM instances (i.e. have executed a KVM_RUN
> ioctl(2) ) only measure events happening inside a guest
> instance. This is only meaningful outside the guests;
> this setting does not change counts gathered inside of a
> guest. Currently this functionality is x86 only.
>
> exclude_guest (since Linux 3.2)
> When conducting measurements that include processes
> running VM instances (i.e. have executed a KVM_RUN
> ioctl(2) ) do not measure events happening inside guest
> instances. This is only meaningful outside the guests;
> this setting does not change counts gathered inside of a
> guest. Currently this functionality is x86 only.
>
>
>
> Signed-off-by: Vince Weaver <vincent.weaver-e7X0jjDqjFGHXe+LvDLADg@public.gmane.org>
>
> diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
> index 638124c..a413c13 100644
> --- a/man2/perf_event_open.2
> +++ b/man2/perf_event_open.2
> @@ -833,10 +833,9 @@ If this bit is set, the count excludes events that happen in kernel-space.
> .IR "exclude_hv"
> If this bit is set, the count excludes events that happen in the
> hypervisor.
> -This is mainly for PMUs that have built-in support for handling this
> -(such as POWER).
> -Extra support is needed for handling hypervisor measurements on most
> -machines.
> +This is mainly for PMUs that have built-in hardware support
> +for this feature (such as POWER; this setting is silently
> +ignored on x86).
> .TP
> .IR "exclude_idle"
> If set, don't count when the CPU is idle.
> @@ -978,10 +977,24 @@ struct sample_id {
> .fi
> .TP
> .IR "exclude_host" " (since Linux 3.2)"
> -Do not measure time spent in VM host.
> +When conducting measurements that include processes running
> +VM instances (i.e. have executed a
> +.I KVM_RUN
> +.BR ioctl (2)
> +) only measure events happening inside a guest instance.
> +This is only meaningful outside the guests; this setting does
> +not change counts gathered inside of a guest.
> +Currently this functionality is x86 only.
> .TP
> .IR "exclude_guest" " (since Linux 3.2)"
> -Do not measure time spent in VM guest.
> +When conducting measurements that include processes running
> +VM instances (i.e. have executed a
> +.I KVM_RUN
> +.BR ioctl (2)
> +) do not measure events happening inside guest instances.
> +This is only meaningful outside the guests; this setting does
> +not change counts gathered inside of a guest.
> +Currently this functionality is x86 only.
> .TP
> .IR "exclude_callchain_kernel" " (since Linux 3.7)"
> Do not include kernel callchains.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-01-06 6:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 15:41 [patch] perf_event_open.2 exclude_host/exclude_guest clarification Vince Weaver
[not found] ` <alpine.DEB.2.11.1412051027470.10310-6xBS8L8d439fDsnSvq7Uqyn2WXadKZNJe7X0jjDqjFGHXe+LvDLADg@public.gmane.org>
2015-01-06 6:45 ` Michael Kerrisk (man-pages) [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-11 19:06 [patch] perf_event_open.2: Exclude_host/exclude_guest clarification Vince Weaver
[not found] ` <alpine.DEB.2.11.1502111405040.16882-6xBS8L8d439fDsnSvq7Uqyn2WXadKZNJe7X0jjDqjFGHXe+LvDLADg@public.gmane.org>
2015-02-17 5:32 ` Michael Kerrisk (man-pages)
[not found] ` <54E2D285.4090502-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-26 7:50 ` Michael Kerrisk (man-pages)
2015-03-03 13:44 ` Joerg Roedel
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=54AB848E.2080808@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=acme-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=gleb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=paulus-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org \
--cc=peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=vincent.weaver-e7X0jjDqjFGHXe+LvDLADg@public.gmane.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).