linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: James Clark <james.clark@linaro.org>
Cc: Thomas Richter <tmricht@linux.ibm.com>,
	Ian Rogers <irogers@google.com>,
	"linux-perf-use." <linux-perf-users@vger.kernel.org>,
	Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
	Leo Yan <leo.yan@arm.com>,
	Sumanth Korikkar <sumanthk@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>
Subject: Re: Perf test 7 fails on s390 since 6.12.0
Date: Tue, 3 Dec 2024 10:10:07 -0800	[thread overview]
Message-ID: <Z09Jf6n9gVxURbsf@google.com> (raw)
In-Reply-To: <8d6d43d1-51be-4412-829a-ef5875321f5b@linaro.org>

Hello,

On Tue, Dec 03, 2024 at 02:37:00PM +0000, James Clark wrote:
> 
> 
> On 02/12/2024 2:53 pm, Thomas Richter wrote:
> > I just downloaded the latest kernel tree 6.13.0rc1 and observed several
> > failures of the perf test suite.
> > 
> > This test case is the first one:
> > # ./perf test -F 7
> > Unrecognized literal '#system_tsc_freq'  7: Simple expression parser  : FAILED!
> > #
> 
> Hi Thomas,
> 
> Did you see this thread: https://lore.kernel.org/linux-perf-users/0F805B2F-35CC-4E0C-BD2F-84552C4C528E@linux.vnet.ibm.com/
> 
> Is that related to your issue? I looked but I couldn't find a V2 from
> Athira.

Oh, I missed this one.  I'll take a look again and let Athira proceed.

> 
> The same test was also mentioned on "[GIT PULL] perf-tools changes for
> v6.13", but I can't tell if it's the same type of failure or not.

I suspect it's the same issue.

Thanks,
Namhyung


  reply	other threads:[~2024-12-03 18:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-02 14:53 Perf test 7 fails on s390 since 6.12.0 Thomas Richter
2024-12-03 14:37 ` James Clark
2024-12-03 18:10   ` Namhyung Kim [this message]
2024-12-04 12:36   ` Thomas Richter

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=Z09Jf6n9gVxURbsf@google.com \
    --to=namhyung@kernel.org \
    --cc=atrajeev@linux.vnet.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=leo.yan@arm.com \
    --cc=linux-perf-users@vger.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;
as well as URLs for NNTP newsgroup(s).