From: Andrew Morton <akpm@linux-foundation.org>
To: kbuild test robot <lkp@intel.com>
Cc: Zong Li <zong.li@sifive.com>,
kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 7592/7905] arch/riscv/mm/ptdump.c:57:3: error: 'FIXADDR_START' undeclared here (not in a function); did you mean 'XAS_RESTART'?
Date: Wed, 13 May 2020 18:07:45 -0700 [thread overview]
Message-ID: <20200513180745.30cfb5d0011c8e12972bdb8d@linux-foundation.org> (raw)
In-Reply-To: <202005091847.zkVHPjis%lkp@intel.com>
On Sat, 9 May 2020 18:46:50 +0800 kbuild test robot <lkp@intel.com> wrote:
> Hi Zong,
>
> First bad commit (maybe != root cause):
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 30e2206e11ce27ae910cc0dab21472429e400a87
> commit: c0eba2d72e70b4208ca6fd82820ba7428090e350 [7592/7905] riscv: support DEBUG_WX
> config: riscv-randconfig-r003-20200509 (attached as .config)
> compiler: riscv64-linux-gcc (GCC) 9.3.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout c0eba2d72e70b4208ca6fd82820ba7428090e350
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day GCC_VERSION=9.3.0 make.cross ARCH=riscv
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All error/warnings (new ones prefixed by >>):
>
> >> arch/riscv/mm/ptdump.c:57:3: error: 'FIXADDR_START' undeclared here (not in a function); did you mean 'XAS_RESTART'?
> 57 | {FIXADDR_START, "Fixmap start"},
> | ^~~~~~~~~~~~~
> | XAS_RESTART
argh, I can't figure out how to make riscv compile :(
Are you using the riscv32 toolchain or riscv64?
And arch/riscv/include/asm/perf_event.h does
#ifdef CONFIG_RISCV_BASE_PMU
#define RISCV_MAX_COUNTERS 2
#endif
#ifndef RISCV_MAX_COUNTERS
#error "Please provide a valid RISCV_MAX_COUNTERS for the PMU."
#endif
where is RISCV_MAX_COUNTERS supposed to come from? Surely this should
be implemented in Kconfig somehow?
Sigh. Zong, did you take a look at this?
next prev parent reply other threads:[~2020-05-14 1:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 10:46 [linux-next:master 7592/7905] arch/riscv/mm/ptdump.c:57:3: error: 'FIXADDR_START' undeclared here (not in a function); did you mean 'XAS_RESTART'? kbuild test robot
2020-05-14 1:07 ` Andrew Morton [this message]
2020-05-14 3:47 ` Zong Li
2020-05-14 8:37 ` Kefeng Wang
2020-05-14 9:19 ` Zong Li
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=20200513180745.30cfb5d0011c8e12972bdb8d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=zong.li@sifive.com \
/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).