From: Nick Kossifidis <mick@ics.forth.gr>
To: linux-riscv@lists.infradead.org
Subject: Perf-related compilation issues
Date: Wed, 23 Oct 2019 18:15:43 +0300 [thread overview]
Message-ID: <1bba622b-1f59-d21b-f396-d9c1a021dc3a@ics.forth.gr> (raw)
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
Hello all,
a) Compiling the current fixes branch with a minimal config I get the
following error:
riscv64-unknown-linux-gnu-ld: arch/riscv/kernel/perf_callchain.o: in
function `.L0 ':
perf_callchain.c:(.text+0x16a): undefined reference to `walk_stackframe'
make: *** [Makefile:1074: vmlinux] Error 1
I've removed the static delcaration of walk_stackframe on stackframe.c
and marked walk_stackframe as extern on perf_callchain.c to fix the
above issue.
b) Then If I compile the kernel without CONFIG_RISCV_BASE_PMU I get
./arch/riscv/include/asm/perf_event.h:26:2: error: #error "Please
provide a valid RISCV_MAX_COUNTERS for the PMU."
#error "Please provide a valid RISCV_MAX_COUNTERS for the PMU."
I noticed that the only place where CONFIG_RISCV_BASE_PMU is checked is
on perf_event.h and only for this parameter that's not defined anywhere
else. So for now if one tries to compile the kernel without PMU the
kernel won't compile + I don't see how unsetting this saves code size as
the config description says.
Since I'm not familiar with the perf code how should I approach this ?
Is the fix on a correct ? How should we handle b ?
Thanks a lot in advance.
Regards,
Nick
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 1795 bytes --]
[-- Attachment #3: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2019-10-23 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 15:15 Nick Kossifidis [this message]
2019-10-23 23:52 ` Perf-related compilation issues Alan Kao
2019-10-24 2:23 ` Paul Walmsley
2019-10-24 6:01 ` Mao Han
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=1bba622b-1f59-d21b-f396-d9c1a021dc3a@ics.forth.gr \
--to=mick@ics.forth.gr \
--cc=linux-riscv@lists.infradead.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).