From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
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: Mon, 23 Jun 2025 14:45:29 -0300 [thread overview]
Message-ID: <aFmSuSyZ1ZNT94Tq@x1> (raw)
In-Reply-To: <CAP-5=fUpnW1DE68pMW0q3vMT+n6d5SeNkwXd45XLaf01-eP47A@mail.gmail.com>
On Mon, Jun 23, 2025 at 08:12:47AM -0700, Ian Rogers wrote:
> On Fri, Jun 20, 2025 at 12:36 PM Namhyung Kim <namhyung@kernel.org> wrote:
> > 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.
> we could do that but in the glibc man page it says:
> https://man7.org/linux/man-pages/man2/prctl.2.html
> ```
> #include <linux/prctl.h> /* Definition of PR_* constants */
> #include <sys/prctl.h>
> ```
> It'd be nice to think musl was slowly getting fixed. I notice we're
Sebastian reported on the musl libc, its maintainer replied:
https://www.openwall.com/lists/musl/2025/06/12/11
- ARnaldo
next prev parent reply other threads:[~2025-06-23 17:45 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
2025-06-23 15:12 ` Ian Rogers
2025-06-23 17:45 ` Arnaldo Carvalho de Melo [this message]
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=aFmSuSyZ1ZNT94Tq@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bigeasy@linutronix.de \
--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).