public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Ondrej Mosnacek <omosnace@redhat.com>
To: git-commits@fedoraproject.org
Subject: [tests/selinux] main: kernel/avc_tracepoint: fix to work on AWS Graviton3 CPUs
Date: Mon, 10 Aug 2026 12:22:51 GMT [thread overview]
Message-ID: <178636457168.1.17159169090767536743.tests-selinux-e7ec6c814805@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : tests/selinux
Branch : main
Commit : e7ec6c814805663203a45a0431e9ed8f9679e778
Author : Ondrej Mosnacek <omosnace@redhat.com>
Date : 2026-08-10T12:04:35+02:00
Stats : +1/-2 in 1 file(s)
URL : https://src.fedoraproject.org/tests/selinux/c/e7ec6c814805663203a45a0431e9ed8f9679e778?branch=main
Log:
kernel/avc_tracepoint: fix to work on AWS Graviton3 CPUs
The --call-graph dwarf argument requires hardware fetures that may not
be implemented on some platforms (e.g. aarch64 AWS Graviton3 CPUs). Use
just plain -g instead, which will hopefully work anywhere. The stack
trace doesn't really matter that much anyway, as we are just testing
that the tracepoint is available and working.
Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
---
diff --git a/kernel/avc_tracepoint/runtest.sh b/kernel/avc_tracepoint/runtest.sh
index d5f292f..2700548 100755
--- a/kernel/avc_tracepoint/runtest.sh
+++ b/kernel/avc_tracepoint/runtest.sh
@@ -15,8 +15,7 @@ rlJournalStart
rlPhaseStartTest
rlAssertExists /sys/kernel/tracing/events/avc/selinux_audited/enable
rlRun "perf list | grep avc:selinux_audited"
- rlRun "perf record -o perf.data -e avc:selinux_audited \
- -g --call-graph dwarf \
+ rlRun "perf record -o perf.data -e avc:selinux_audited -g \
runcon system_u:system_r:kernel_t:s0 echo" 0-255
rlRun "perf script -i perf.data"
rlAssertGreater "'perf script' output should have more than 0 lines" \
reply other threads:[~2026-08-10 12:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=178636457168.1.17159169090767536743.tests-selinux-e7ec6c814805@fedoraproject.org \
--to=omosnace@redhat.com \
--cc=git-commits@fedoraproject.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