mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ravi Bangoria <ravi.bangoria@amd.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: 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>,
	Namhyung Kim <namhyung@kernel.org>,
	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: Sat, 17 May 2025 17:33:19 +0530	[thread overview]
Message-ID: <33e86415-c90d-420a-b7a8-6a360769aea4@amd.com> (raw)
In-Reply-To: <aCfuGXUnNIbnYo_r@x1>

Hi Arnaldo,

> 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?

2) "mprotect() failed. Permission denied" seems to be because of
   SELinux enforced mode? I'll prepare and post a fix but, even
   with the error, it's just part of the dummy workload function
   so wouldn't break any test functionality.

Thanks,
Ravi

  reply	other threads:[~2025-05-17 12:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-17  2:02 Arnaldo Carvalho de Melo
2025-05-17 12:03 ` Ravi Bangoria [this message]
2025-05-18 18:22   ` Namhyung Kim
2025-05-19 16:39     ` Ravi Bangoria
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=33e86415-c90d-420a-b7a8-6a360769aea4@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
all inboxes | Powered by JetHome®