public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Martin Kaiser <martin@kaiser.cx>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ian Rogers <irogers@google.com>,
	James Clark <james.clark@linaro.org>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] perf: fix some tests for musl
Date: Tue, 28 Apr 2026 16:09:55 -0700	[thread overview]
Message-ID: <afE-QzduLVrSaZcO@google.com> (raw)
In-Reply-To: <20260428143920.2466185-1-martin@kaiser.cx>

On Tue, Apr 28, 2026 at 04:38:45PM +0200, Martin Kaiser wrote:
> Fix some perf tests for systems that use musl instead of glibc.
> 
> v2:
> - add Namhyung's Acked-by for patch 1
> - stricter flags check for patch 2
> - more generic workload in patch 3
> 
> Martin Kaiser (3):
>   perf test: fix nanosleep check in the ftrace test
>   perf test: fix sys_enter_openat event test for musl
>   perf test: fix "trace summary" test for musl-based systems

Acked-by: Namhyung Kim <namhyung@kernel.org>

Thanks,
Namhyung

> 
>  tools/perf/tests/openat-syscall-tp-fields.c | 5 ++++-
>  tools/perf/tests/shell/ftrace.sh            | 7 ++++---
>  tools/perf/tests/shell/trace_summary.sh     | 2 +-
>  3 files changed, 9 insertions(+), 5 deletions(-)
> 
> -- 
> 2.43.7
> 

      parent reply	other threads:[~2026-04-28 23:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28 14:38 [PATCH v2 0/3] perf: fix some tests for musl Martin Kaiser
2026-04-28 14:38 ` [PATCH v2 1/3] perf test: fix nanosleep check in the ftrace test Martin Kaiser
2026-04-28 14:38 ` [PATCH v2 2/3] perf test: fix sys_enter_openat event test for musl Martin Kaiser
2026-04-29 16:55   ` Ian Rogers
2026-04-30  7:15     ` Martin Kaiser
2026-04-28 14:38 ` [PATCH v2 3/3] perf test: fix "trace summary" test for musl-based systems Martin Kaiser
2026-04-29 16:57   ` Ian Rogers
2026-04-28 23:09 ` Namhyung Kim [this message]

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=afE-QzduLVrSaZcO@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=martin@kaiser.cx \
    --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