From: Ravi Bangoria <ravi.bangoria@amd.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Ian Rogers <irogers@google.com>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
Ravi Bangoria <ravi.bangoria@amd.com>
Subject: Re: IBS perf test failures on 9950x3d
Date: Mon, 19 May 2025 22:09:21 +0530 [thread overview]
Message-ID: <d8e45b04-d746-4af9-a55c-c3e46f8f952c@amd.com> (raw)
In-Reply-To: <aColYM3RqE4T5t5c@google.com>
Hi Namhyung,
>>> If it needs a specific kernel, then the test needs to cope with that,
>>> etc.
>>
>> 1) Bunch of IBS kernel fixes went in recently (v6.15-rc1):
>>
>> https://lore.kernel.org/r/20250115054438.1021-1-ravi.bangoria@amd.com
>>
>> Since you are running on 6.14.5-300.fc42.x86_64, the failures are
>> genuine and indicating that kernel should be fixed.
>>
>> I'm wondering how would the test cope with the buggy kernel. Or
>> probably 'perf test' a wrong place to put such selftests?
>
> Maybe... some kernel internal changes can be tested in the selftest.
>
> And 'perf test' should work with any kernel versions. Is the test
> checking any invalid configs? Probably then it should move to the
> selftest so that it can be tied to the fixed kernels and 'perf test'
> should only use valid configs.
Sure. I'll prepare a patch to move this test from 'perf test' to
tools/testing/selftest/.
Thanks,
Ravi
next prev parent reply other threads:[~2025-05-19 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 2:02 IBS perf test failures on 9950x3d Arnaldo Carvalho de Melo
2025-05-17 12:03 ` Ravi Bangoria
2025-05-18 18:22 ` Namhyung Kim
2025-05-19 16:39 ` Ravi Bangoria [this message]
2025-05-19 18:28 ` Arnaldo Carvalho de Melo
2025-05-20 11:01 ` Ravi Bangoria
2025-05-20 20:47 ` Arnaldo Carvalho de Melo
2025-05-21 20:50 ` 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=d8e45b04-d746-4af9-a55c-c3e46f8f952c@amd.com \
--to=ravi.bangoria@amd.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.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).