From: Vince Weaver <vincent.weaver@maine.edu>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Vince Weaver <vincent.weaver@maine.edu>,
linux-man@vger.kernel.org, linux-kernel@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [patch] perf_event_open.2: PERF_RECORD_SWITCH support
Date: Wed, 19 Oct 2016 11:14:33 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.20.1610191111090.16261@macbook-air> (raw)
In-Reply-To: <15d30ad2-2937-febe-d6c9-b8dded4642d8@gmail.com>
On Wed, 19 Oct 2016, Michael Kerrisk (man-pages) wrote:
> > diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
> > index 68b99bb..04a0cf5 100644
> > +.B PERF_RECORD_SWITCH_CPU_WIDE
> > +records when sampling in cpu-wide mode.
> > +This functionality is in addition to existing tracepoint and
> > +software events for measuring context switches.
> > +The advantage of this method is that it will give full
>
> s/give full/give a full/
>
> ok?
>
> > +information event with strict
> > +.I perf_event_paranoid
> > +settings.
What I meant to say was
"it will give full information *even* with strict perf_event_paranoid
settings"
Maybe saying something like "despite strict settings" would be better
wording.
not sure how I missed that typo, apparently my fingers are used to typing
"event" too much.
Vince
next prev parent reply other threads:[~2016-10-19 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 17:22 Vince Weaver
2016-10-19 7:00 ` Michael Kerrisk (man-pages)
2016-10-19 15:14 ` Vince Weaver [this message]
2016-10-20 5:49 ` Michael Kerrisk (man-pages)
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=alpine.DEB.2.20.1610191111090.16261@macbook-air \
--to=vincent.weaver@maine.edu \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®