linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "David Prévot" <taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] perf_event_open.2: ffix
Date: Wed, 04 Sep 2013 08:12:22 +0200	[thread overview]
Message-ID: <5226CF46.9020703@gmail.com> (raw)
In-Reply-To: <1378178181-12859-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>

Thanks, David. Applied.

Cheers,

Michael


On 09/03/13 05:16, David Prévot wrote:
> ---
>  man2/perf_event_open.2 | 10 ++++++----
>  1 file changed, 6 insertions(+), 4 deletions(-)
> 
> diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
> index c7f577d..f96df8c 100644
> --- a/man2/perf_event_open.2
> +++ b/man2/perf_event_open.2
> @@ -164,7 +164,7 @@ This flag re-routes the output from an event to the group leader.
>  This flag activates per-container system-wide monitoring.
>  A container
>  is an abstraction that isolates a set of resources for finer grain
> -control (CPUs, memory, etc...).
> +control (CPUs, memory, etc.).
>  In this mode, the event is measured
>  only if the thread running on the monitored CPU belongs to the designated
>  container (cgroup).
> @@ -2010,15 +2010,17 @@ Each entry has an optional value (either hex or decimal).
>  If no value is specified than it is assumed to be a single-bit
>  field with a value of 1.
>  An example entry may look like this:
> -.I event=0x2,inv,ldlat=3
> +.IR event=0x2,inv,ldlat=3 .
>  .TP
>  .I /sys/bus/event_source/devices/*/uevent
>  This file is the standard kernel device interface
>  for injecting hotplug events.
>  .TP
>  .IR /sys/bus/event_source/devices/*/cpumask " (Since Linux 3.7)"
> -The cpumask file contains a comma-separated list of integers that
> -indicate a representative cpu number for each socket (package)
> +The
> +.I cpumask
> +file contains a comma-separated list of integers that
> +indicate a representative CPU number for each socket (package)
>  on the motherboard.
>  This is needed when setting up uncore or northbridge events, as
>  those PMUs present socket-wide events.
> 

--
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

  parent reply	other threads:[~2013-09-04  6:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03  3:16 [PATCH] perf_event_open.2: ffix David Prévot
     [not found] ` <1378178181-12859-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2013-09-04  6:12   ` Michael Kerrisk (man-pages) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-12-15 22:16 David Prévot
     [not found] ` <1387145797-3597-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2013-12-26 18:43   ` 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=5226CF46.9020703@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=taffit-8fiUuRrzOP0dnm+yROfE0A@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).