All of lore.kernel.org
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: open list <linux-kernel@vger.kernel.org>,
	linux-trace-kernel@vger.kernel.org,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	lkft-triage@lists.linaro.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Anders Roxell <anders.roxell@linaro.org>
Subject: selftests: ftrace: event filter function - test event filtering on functions [FAIL]
Date: Tue, 14 Mar 2023 15:52:44 +0530	[thread overview]
Message-ID: <CA+G9fYtF-XEKi9YNGgR=Kf==7iRb2FrmEC7qtwAeQbfyah-UhA@mail.gmail.com> (raw)

Results from Linaro’s test farm.

selftests ftrace failed on qemu-x86_64 and qemu-arm64.
Please find the test log below.

Is this expected to fail ? Am I missing anything ?

Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>

kselftest: Running tests in ftrace
TAP version 13
1..1
# selftests: ftrace: ftracetest
# === Ftrace unit tests ===
# [1] Basic trace file check [PASS]

...

# [23] event filter function - test event filtering on functions [FAIL]

...
# [58] Kretprobe %return suffix test [PASS]
# [59] Register/unregister many kprobe events
[  431.662904] trace_kprobe: Could not probe notrace function startup_64
[  431.669846] trace_kprobe: Could not probe notrace function _stext
[  431.674104] trace_kprobe: Could not probe notrace function _text
[  431.675908] trace_kprobe: Could not probe notrace function
secondary_startup_64
[  431.677876] trace_kprobe: Could not probe notrace function
secondary_startup_64_no_verify
[  431.679899] trace_kprobe: Could not probe notrace function __pfx_verify_cpu
[  431.681738] trace_kprobe: Could not probe notrace function verify_cpu
[  431.683667] trace_kprobe: Could not probe notrace function
__pfx_sev_verify_cbit
[  431.685594] trace_kprobe: Could not probe notrace function sev_verify_cbit
[  431.687381] trace_kprobe: Could not probe notrace function start_cpu0
[  431.689225] trace_kprobe: Could not probe notrace function __pfx___startup_64
[  431.691223] trace_kprobe: Could not probe notrace function __startup_64
[  431.693088] trace_kprobe: Could not probe notrace function
__pfx_startup_64_setup_env
[  431.695021] trace_kprobe: Could not probe notrace function
startup_64_setup_env
[  431.697012] trace_kprobe: Could not probe notrace function
__pfx___traceiter_initcall_level
[  431.700780] trace_kprobe: Could not probe notrace function
__pfx___traceiter_initcall_start
...
[  439.183587] trace_kprobe: Could not probe notrace function
__pfx_hv_check_msr_access
[  439.186192] trace_kprobe: Could not probe notrace function
__pfx_kvm_hv_flush_tlb
...

# [106] (instance)  event filter function - test event filtering on
functions [FAIL]

...
#
# # of passed:  109
# # of failed:  2
# # of unresolved:  3
# # of untested:  0
# # of unsupported:  3
# # of xfailed:  1
# # of undefined(test bug):  0
not ok 1 selftests: ftrace: ftracetest # exit=1

log link,
https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230314/testrun/15564370/suite/kselftest-ftrace/test/ftrace_ftracetest/log

--
Linaro LKFT
https://lkft.linaro.org

             reply	other threads:[~2023-03-14 10:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 10:22 Naresh Kamboju [this message]
2023-03-14 13:50 ` selftests: ftrace: event filter function - test event filtering on functions [FAIL] Steven Rostedt
2023-03-15  8:32 ` Masami Hiramatsu
2023-03-15  9:11   ` Naresh Kamboju
2023-03-18 15:27     ` Masami Hiramatsu

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='CA+G9fYtF-XEKi9YNGgR=Kf==7iRb2FrmEC7qtwAeQbfyah-UhA@mail.gmail.com' \
    --to=naresh.kamboju@linaro.org \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=mhiramat@kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.