From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, kbuild-all@01.org
Subject: Re: [powerpc:next-test 70/71] include/asm-generic/memory_model.h:55:54: error: 'vmemmap' undeclared; did you mean 'mem_map'?
Date: Wed, 12 Dec 2018 08:23:54 +0100 [thread overview]
Message-ID: <4bd298cc-a03a-5a01-aa2f-1ca8e6838fa3@c-s.fr> (raw)
In-Reply-To: <201812121310.MnbC0L9L%fengguang.wu@intel.com>
This one is already fixed in v2 and v3 by the addition of asm/pgtable.h
Christophe
Le 12/12/2018 à 06:36, kbuild test robot a écrit :
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next-test
> head: 13fd174be1903cc069bb73b0d53a0420b8f6d778
> commit: 3a0f466ce2402cc090c97ccc1285508f688d8a8e [70/71] powerpc: Implement CONFIG_DEBUG_VIRTUAL
> config: powerpc-ppc64e_defconfig (attached as .config)
> compiler: powerpc64-linux-gnu-gcc (Debian 7.2.0-11) 7.2.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 3a0f466ce2402cc090c97ccc1285508f688d8a8e
> # save the attached .config to linux build tree
> GCC_VERSION=7.2.0 make.cross ARCH=powerpc
>
> All errors (new ones prefixed by >>):
>
> In file included from arch/powerpc/include/asm/page.h:339:0,
> from arch/powerpc/include/asm/thread_info.h:29,
> from include/linux/thread_info.h:38,
> from include/asm-generic/preempt.h:5,
> from ./arch/powerpc/include/generated/asm/preempt.h:1,
> from include/linux/preempt.h:81,
> from include/linux/spinlock.h:51,
> from include/linux/seqlock.h:36,
> from include/linux/time.h:6,
> from include/linux/stat.h:19,
> from include/linux/module.h:10,
> from init/do_mounts.c:1:
> arch/powerpc/include/asm/io.h: In function 'page_to_phys':
>>> include/asm-generic/memory_model.h:55:54: error: 'vmemmap' undeclared (first use in this function); did you mean 'mem_map'?
> #define __page_to_pfn(page) (unsigned long)((page) - vmemmap)
> ^
> include/asm-generic/memory_model.h:81:21: note: in expansion of macro '__page_to_pfn'
> #define page_to_pfn __page_to_pfn
> ^~~~~~~~~~~~~
> arch/powerpc/include/asm/io.h:835:22: note: in expansion of macro 'page_to_pfn'
> unsigned long pfn = page_to_pfn(page);
> ^~~~~~~~~~~
> include/asm-generic/memory_model.h:55:54: note: each undeclared identifier is reported only once for each function it appears in
> #define __page_to_pfn(page) (unsigned long)((page) - vmemmap)
> ^
> include/asm-generic/memory_model.h:81:21: note: in expansion of macro '__page_to_pfn'
> #define page_to_pfn __page_to_pfn
> ^~~~~~~~~~~~~
> arch/powerpc/include/asm/io.h:835:22: note: in expansion of macro 'page_to_pfn'
> unsigned long pfn = page_to_pfn(page);
> ^~~~~~~~~~~
>
> vim +55 include/asm-generic/memory_model.h
>
> 8f6aac41 Christoph Lameter 2007-10-16 52
> af901ca1 André Goddard Rosa 2009-11-14 53 /* memmap is virtually contiguous. */
> 8f6aac41 Christoph Lameter 2007-10-16 54 #define __pfn_to_page(pfn) (vmemmap + (pfn))
> 32272a26 Martin Schwidefsky 2008-12-25 @55 #define __page_to_pfn(page) (unsigned long)((page) - vmemmap)
> 8f6aac41 Christoph Lameter 2007-10-16 56
>
> :::::: The code at line 55 was first introduced by commit
> :::::: 32272a26974d2027384fd4010cd1780fca425d94 [S390] __page_to_pfn warnings
>
> :::::: TO: Martin Schwidefsky <schwidefsky@de.ibm.com>
> :::::: CC: Martin Schwidefsky <schwidefsky@de.ibm.com>
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
>
prev parent reply other threads:[~2018-12-12 7:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 5:36 [powerpc:next-test 70/71] include/asm-generic/memory_model.h:55:54: error: 'vmemmap' undeclared; did you mean 'mem_map'? kbuild test robot
2018-12-12 7:23 ` Christophe Leroy [this message]
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=4bd298cc-a03a-5a01-aa2f-1ca8e6838fa3@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=kbuild-all@01.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox