linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Clark <james.clark@arm.com>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Kan Liang <kan.liang@linux.intel.com>,
	Changbin Du <changbin.du@huawei.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] perf docs: Fix typos
Date: Tue, 28 May 2024 16:55:57 +0100	[thread overview]
Message-ID: <669d0fcf-5afa-45c5-a836-eccad0884d33@arm.com> (raw)
In-Reply-To: <20240521223555.858859-1-irogers@google.com>



On 21/05/2024 23:35, Ian Rogers wrote:
> Assorted typo fixes.
> 
> Signed-off-by: Ian Rogers <irogers@google.com>

Reviewed-by: James Clark <james.clark@arm.com>

> ---
>  tools/perf/Documentation/perf-kwork.txt  | 4 ++--
>  tools/perf/Documentation/perf-mem.txt    | 2 +-
>  tools/perf/Documentation/perf-record.txt | 2 +-
>  3 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/tools/perf/Documentation/perf-kwork.txt b/tools/perf/Documentation/perf-kwork.txt
> index 109ace1d5e90..21e607669d78 100644
> --- a/tools/perf/Documentation/perf-kwork.txt
> +++ b/tools/perf/Documentation/perf-kwork.txt
> @@ -1,4 +1,4 @@
> -perf-kowrk(1)
> +perf-kwork(1)
>  =============
>  
>  NAME
> @@ -35,7 +35,7 @@ There are several variants of 'perf kwork':
>          perf kwork top
>          perf kwork top -b
>  
> -   By default it shows the individual work events such as irq, workqeueu,
> +   By default it shows the individual work events such as irq, workqueue,
>     including the run time and delay (time between raise and actually entry):
>  
>        Runtime start      Runtime end        Cpu     Kwork name                 Runtime     Delaytime
> diff --git a/tools/perf/Documentation/perf-mem.txt b/tools/perf/Documentation/perf-mem.txt
> index 19862572e3f2..47456b212e99 100644
> --- a/tools/perf/Documentation/perf-mem.txt
> +++ b/tools/perf/Documentation/perf-mem.txt
> @@ -21,7 +21,7 @@ and stores are sampled. Use the -t option to limit to loads or stores.
>  
>  Note that on Intel systems the memory latency reported is the use-latency,
>  not the pure load (or store latency). Use latency includes any pipeline
> -queueing delays in addition to the memory subsystem latency.
> +queuing delays in addition to the memory subsystem latency.
>  
>  On Arm64 this uses SPE to sample load and store operations, therefore hardware
>  and kernel support is required. See linkperf:perf-arm-spe[1] for a setup guide.
> diff --git a/tools/perf/Documentation/perf-record.txt b/tools/perf/Documentation/perf-record.txt
> index 6015fdd08fb6..77578c0a142a 100644
> --- a/tools/perf/Documentation/perf-record.txt
> +++ b/tools/perf/Documentation/perf-record.txt
> @@ -311,7 +311,7 @@ OPTIONS
>  	User can change the size by passing the size after comma like
>  	"--call-graph dwarf,4096".
>  
> -	When "fp" recording is used, perf tries to save stack enties
> +	When "fp" recording is used, perf tries to save stack entries
>  	up to the number specified in sysctl.kernel.perf_event_max_stack
>  	by default.  User can change the number by passing it after comma
>  	like "--call-graph fp,32".

  reply	other threads:[~2024-05-28 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21 22:35 [PATCH v1] perf docs: Fix typos Ian Rogers
2024-05-28 15:55 ` James Clark [this message]
2024-05-29 19:27 ` Namhyung Kim

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=669d0fcf-5afa-45c5-a836-eccad0884d33@arm.com \
    --to=james.clark@arm.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=changbin.du@huawei.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).