public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@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>,
	James Clark <james.clark@linaro.org>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/5] perf test: Remove parallel option documentation
Date: Thu, 9 Jan 2025 16:58:53 -0800	[thread overview]
Message-ID: <Z4BwzZ27OrG19EL7@google.com> (raw)
In-Reply-To: <20250109215055.454888-4-irogers@google.com>

On Thu, Jan 09, 2025 at 01:50:53PM -0800, Ian Rogers wrote:
> The parallel option was removed in commit 94d1a913bdc4 ("perf test:
> Make parallel testing the default").
> 
> Fixes: 94d1a913bdc4 ("perf test: Make parallel testing the default")
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
>  tools/perf/Documentation/perf-test.txt | 6 ------
>  1 file changed, 6 deletions(-)
> 
> diff --git a/tools/perf/Documentation/perf-test.txt b/tools/perf/Documentation/perf-test.txt
> index efcdec528a8f..8f8a3c367570 100644
> --- a/tools/perf/Documentation/perf-test.txt
> +++ b/tools/perf/Documentation/perf-test.txt
> @@ -35,12 +35,6 @@ OPTIONS
>  --sequential::
>  	Run tests one after the other, this is the default mode.

This needs to be changed too as it's not the default anymore. :)

Thanks,
Namhyung

>  
> --p:: 
> ---parallel::
> -	Run tests in parallel, speeds up the whole process but is not safe with
> -	the current infrastructure, where some tests that compete for some resources,
> -	for instance, 'perf probe' tests that add/remove probes or clean all probes, etc.
> -
>  -F::
>  --dont-fork::
>  	Do not fork child for each test, run all tests within single process, this
> -- 
> 2.47.1.613.gc27f4b7a9f-goog
> 

  reply	other threads:[~2025-01-10  0:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09 21:50 [PATCH v4 0/5] perf test: Add a runs-per-test option Ian Rogers
2025-01-09 21:50 ` [PATCH v4 1/5] perf test: Rename functions and variables for better clarity Ian Rogers
2025-01-09 21:50 ` [PATCH v4 2/5] perf test: Send list output to stdout rather than stderr Ian Rogers
2025-01-09 21:50 ` [PATCH v4 3/5] perf test: Remove parallel option documentation Ian Rogers
2025-01-10  0:58   ` Namhyung Kim [this message]
2025-01-10  4:46     ` Ian Rogers
2025-01-09 21:50 ` [PATCH v4 4/5] perf test: Add a runs-per-test flag Ian Rogers
2025-01-09 21:50 ` [PATCH v4 5/5] perf test: Improve verbose documentation Ian Rogers

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=Z4BwzZ27OrG19EL7@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --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=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