All of lore.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 linux-next] perf test: Fix test perf evlist for z/VM s390x
Date: Mon, 26 Jan 2026 17:34:37 -0300	[thread overview]
Message-ID: <aXfP3avz62ZM14bE@x1> (raw)
In-Reply-To: <CAP-5=fXPGXJMDPQc4XxrEWW_HgJTbrbL6g1xfTBn14jDiW0Yxw@mail.gmail.com>

On Mon, Jan 26, 2026 at 09:42:54AM -0800, Ian Rogers wrote:
> On Mon, Jan 26, 2026 at 2:18 AM Thomas Richter <tmricht@linux.ibm.com> wrote:
> >
> > Perf test case 'perf evlist tests' fails on z/VM machines on s390.
> >
> > The failure is causes by event cycles. This event is not available
> > on virtualized machines like z/VM on s390.
> > Change to software event cpu-clock to fix this.
> >
> >     Output before:
> >       # ./perf test 78
> >       79: perf evlist tests              : FAILED!
> >       #
> >
> >     Output after:
> >       # ./perf test 78
> >       79: perf evlist tests              : Ok
> >       #
> >
> > Fixes: b04d2b919912 ("perf test: Fix test case perf evlist tests for s390x")
> > Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
> > Tested-by: Jan Polensky <japo@linux.ibm.com>
> > Reviewed-by: Jan Polensky <japo@linux.ibm.com>
> > Cc: Ian Rogers <irogers@google.com>

> Reviewed-by: Ian Rogers <irogers@google.com>

Thanks, applied to perf-tools-next,

- Arnaldo

      reply	other threads:[~2026-01-26 20:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-26 10:18 [PATCH linux-next] perf test: Fix test perf evlist for z/VM s390x Thomas Richter
2026-01-26 17:42 ` Ian Rogers
2026-01-26 20:34   ` 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=aXfP3avz62ZM14bE@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 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.