public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Thomas Richter <tmricht@linux.ibm.com>,
	linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	linux-perf-users@vger.kernel.org, namhyung@kernel.org,
	agordeev@linux.ibm.com, gor@linux.ibm.com,
	sumanthk@linux.ibm.com, hca@linux.ibm.com, japo@linux.ibm.com
Subject: Re: [PATCH v2] perf test: Fix test case perf evlist tests for s390x
Date: Tue, 6 Jan 2026 18:43:34 -0300	[thread overview]
Message-ID: <aV2CBqwc94wbPCsQ@x1> (raw)
In-Reply-To: <CAP-5=fXZw9NA7bK6bH+hxPYG0nHGPYKqtYt3pg7iNmsQPWHRig@mail.gmail.com>

On Wed, Dec 10, 2025 at 10:35:01AM -0800, Ian Rogers wrote:
> On Tue, Dec 9, 2025 at 11:18 PM Thomas Richter <tmricht@linux.ibm.com> wrote:
> >
> > Perf test case 78: perf evlist tests fails on s390. The failure
> > is causes by grouping events cycles and instructions because
> > sampling does only support event cycles.
> > Change the group to software events to fix this.
> >
> > Output before:
> >   # ./perf test 78
> >   78: perf evlist tests              : FAILED!
> >   #
> >
> > Output after:
> >   # ./perf test 78
> >   78: perf evlist tests              : Ok
> >   #
> >
> > Fixes: db452961de939 ("perf tests evlist: Add basic evlist test")
> > Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
> 
> Tested-by: Ian Rogers <irogers@google.com>

Thanks, applied to perf-tools-next,

- Arnaldo

      reply	other threads:[~2026-01-06 21:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-10  7:17 [PATCH v2] perf test: Fix test case perf evlist tests for s390x Thomas Richter
2025-12-10 18:35 ` Ian Rogers
2026-01-06 21:43   ` Arnaldo Carvalho de Melo [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=aV2CBqwc94wbPCsQ@x1 \
    --to=acme@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=irogers@google.com \
    --cc=japo@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=sumanthk@linux.ibm.com \
    --cc=tmricht@linux.ibm.com \
    /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