All of lore.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>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2 1/2] perf test workload noploop: Name the noploop process
Date: Fri, 20 Jun 2025 12:36:52 -0700	[thread overview]
Message-ID: <aFW4VJtk96JD865U@google.com> (raw)
In-Reply-To: <20250619002034.97007-1-irogers@google.com>

Hi Ian,

On Wed, Jun 18, 2025 at 05:20:33PM -0700, Ian Rogers wrote:
> Name the noploop process "perf-noploop" so that tests can easily check
> for its existence.
> 
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
>  tools/perf/tests/workloads/noploop.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/tools/perf/tests/workloads/noploop.c b/tools/perf/tests/workloads/noploop.c
> index 940ea5910a84..8b954d466083 100644
> --- a/tools/perf/tests/workloads/noploop.c
> +++ b/tools/perf/tests/workloads/noploop.c
> @@ -2,6 +2,8 @@
>  #include <stdlib.h>
>  #include <signal.h>
>  #include <unistd.h>
> +#include <linux/prctl.h>
> +#include <sys/prctl.h>

I'm afraid it'd introduce a build failure on musl.  Please see

https://lore.kernel.org/linux-perf-users/20250611092542.F4ooE2FL@linutronix.de/

I think <sys/prctl.h> would be enough.

Thanks,
Namhyung


>  #include <linux/compiler.h>
>  #include "../tests.h"
>  
> @@ -16,6 +18,7 @@ static int noploop(int argc, const char **argv)
>  {
>  	int sec = 1;
>  
> +	prctl(PR_SET_NAME, "perf-noploop");
>  	if (argc > 0)
>  		sec = atoi(argv[0]);
>  
> -- 
> 2.50.0.rc2.701.gf1e915cc24-goog
> 

  parent reply	other threads:[~2025-06-20 19:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19  0:20 [PATCH v2 1/2] perf test workload noploop: Name the noploop process Ian Rogers
2025-06-19  0:20 ` [PATCH v2 2/2] perf test: Add sched latency and script shell tests Ian Rogers
2025-06-20 10:01   ` James Clark
2025-06-20 19:41   ` Namhyung Kim
2025-06-28  1:25     ` Ian Rogers
2025-06-20 10:01 ` [PATCH v2 1/2] perf test workload noploop: Name the noploop process James Clark
2025-06-20 19:36 ` Namhyung Kim [this message]
2025-06-23 15:12   ` Ian Rogers
2025-06-23 17:45     ` Arnaldo Carvalho de Melo
2025-06-23 18:05       ` Ian Rogers
2025-06-23 18:14         ` Namhyung Kim
2025-06-23 19:18           ` Arnaldo Carvalho de Melo
2025-06-23 19:41             ` Ian Rogers
2025-06-23 23:14               ` 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=aFW4VJtk96JD865U@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.