All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Rob Herring <robh@kernel.org>, Catalin Marinas <catalin.marinas@arm.com>
Cc: kernel test robot <lkp@intel.com>,
	Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
	kbuild-all@lists.01.org,
	clang-built-linux <clang-built-linux@googlegroups.com>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 6272/9613] unittest.c:undefined reference to `of_dma_get_max_cpu_address'
Date: Tue, 1 Dec 2020 15:40:34 -0800	[thread overview]
Message-ID: <98b2ba67-d43b-c285-8ad0-20e52c1d3227@infradead.org> (raw)
In-Reply-To: <CAL_Jsq+iRn3YdTi_PBkDoY86mJkSp=1-oKmG+Fsz8HrEwyNNhA@mail.gmail.com>

On 12/1/20 12:13 PM, Rob Herring wrote:
> On Tue, Dec 1, 2020 at 5:29 AM Catalin Marinas <catalin.marinas@arm.com> wrote:
>>
>> On Tue, Dec 01, 2020 at 05:32:51PM +0800, kernel test robot wrote:
>>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>>> head:   c6b11acc5f85b6e11d128fad8e0b7b223aa7e33f
>>> commit: 07d13a1d6120d453c3c1f020578693d072deded5 [6272/9613] of: unittest: Add test for of_dma_get_max_cpu_address()
>>> config: s390-randconfig-r034-20201201 (attached as .config)
>>> compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project ac40a2d8f16b8a8c68fc811d67f647740e965cb8)
>>> reproduce (this is a W=1 build):
>>>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>>>         chmod +x ~/bin/make.cross
>>>         # install s390 cross compiling tool for clang build
>>>         # apt-get install binutils-s390x-linux-gnu
>>>         # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=07d13a1d6120d453c3c1f020578693d072deded5
>>>         git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>>>         git fetch --no-tags linux-next master
>>>         git checkout 07d13a1d6120d453c3c1f020578693d072deded5
>>>         # save the attached .config to linux build tree
>>>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=s390
>>>
>>> If you fix the issue, kindly add following tag as appropriate
>>> Reported-by: kernel test robot <lkp@intel.com>
>>>
>>> All errors (new ones prefixed by >>):
>>>
>>>    s390x-linux-gnu-ld: kernel/dma/coherent.o: in function `dma_declare_coherent_memory':
>>>    coherent.c:(.text+0xf8): undefined reference to `memunmap'
>>>    s390x-linux-gnu-ld: kernel/dma/coherent.o: in function `dma_init_coherent_memory':
>>>    coherent.c:(.text+0x174): undefined reference to `memremap'
>>>    s390x-linux-gnu-ld: coherent.c:(.text+0x344): undefined reference to `memunmap'
>>>    s390x-linux-gnu-ld: drivers/of/unittest.o: in function `of_unittest':
>>>>> unittest.c:(.init.text+0x120): undefined reference to `of_dma_get_max_cpu_address'
>>
>> Thanks for the report. I think it needs the diff below. If Rob/Nicolas
>> are ok with it, I'll add it to the arm64 tree (with some commit text):
>>
>> diff --git a/drivers/of/unittest.c b/drivers/of/unittest.c
>> index 98cc0163301b..799125ef66fc 100644
>> --- a/drivers/of/unittest.c
>> +++ b/drivers/of/unittest.c
>> @@ -871,6 +871,7 @@ static void __init of_unittest_changeset(void)
>>
>>  static void __init of_unittest_dma_get_max_cpu_address(void)
>>  {
>> +#ifdef CONFIG_OF_ADDRESS
> 
>        if (!IS_ENABLED(CONFIG_OF_ADDRESS))
>                return;
> 
> This once again makes me want to kill off HAS_IOMEM. Or at least
> always have a dummy ioremap() and friends for !HAS_IOMEM.

That would eliminate dozens of build errors on S390 when
# CONFIG_HAS_IOMEM is not set
# CONFIG_OF_ADDRESS is not set

>>         struct device_node *np;
>>         phys_addr_t cpu_addr;
>>
>> @@ -884,6 +885,7 @@ static void __init of_unittest_dma_get_max_cpu_address(void)
>>         unittest(cpu_addr == 0x4fffffff,
>>                  "of_dma_get_max_cpu_address: wrong CPU addr %pad (expecting %x)\n",
>>                  &cpu_addr, 0x4fffffff);
>> +#endif
>>  }
>>
>>  static void __init of_unittest_dma_ranges_one(const char *path,
>>
>> --
>> Catalin
> 


-- 
~Randy



WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <rdunlap@infradead.org>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 6272/9613] unittest.c:undefined reference to `of_dma_get_max_cpu_address'
Date: Tue, 01 Dec 2020 15:40:34 -0800	[thread overview]
Message-ID: <98b2ba67-d43b-c285-8ad0-20e52c1d3227@infradead.org> (raw)
In-Reply-To: <CAL_Jsq+iRn3YdTi_PBkDoY86mJkSp=1-oKmG+Fsz8HrEwyNNhA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3524 bytes --]

On 12/1/20 12:13 PM, Rob Herring wrote:
> On Tue, Dec 1, 2020 at 5:29 AM Catalin Marinas <catalin.marinas@arm.com> wrote:
>>
>> On Tue, Dec 01, 2020 at 05:32:51PM +0800, kernel test robot wrote:
>>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>>> head:   c6b11acc5f85b6e11d128fad8e0b7b223aa7e33f
>>> commit: 07d13a1d6120d453c3c1f020578693d072deded5 [6272/9613] of: unittest: Add test for of_dma_get_max_cpu_address()
>>> config: s390-randconfig-r034-20201201 (attached as .config)
>>> compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project ac40a2d8f16b8a8c68fc811d67f647740e965cb8)
>>> reproduce (this is a W=1 build):
>>>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>>>         chmod +x ~/bin/make.cross
>>>         # install s390 cross compiling tool for clang build
>>>         # apt-get install binutils-s390x-linux-gnu
>>>         # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=07d13a1d6120d453c3c1f020578693d072deded5
>>>         git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>>>         git fetch --no-tags linux-next master
>>>         git checkout 07d13a1d6120d453c3c1f020578693d072deded5
>>>         # save the attached .config to linux build tree
>>>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=s390
>>>
>>> If you fix the issue, kindly add following tag as appropriate
>>> Reported-by: kernel test robot <lkp@intel.com>
>>>
>>> All errors (new ones prefixed by >>):
>>>
>>>    s390x-linux-gnu-ld: kernel/dma/coherent.o: in function `dma_declare_coherent_memory':
>>>    coherent.c:(.text+0xf8): undefined reference to `memunmap'
>>>    s390x-linux-gnu-ld: kernel/dma/coherent.o: in function `dma_init_coherent_memory':
>>>    coherent.c:(.text+0x174): undefined reference to `memremap'
>>>    s390x-linux-gnu-ld: coherent.c:(.text+0x344): undefined reference to `memunmap'
>>>    s390x-linux-gnu-ld: drivers/of/unittest.o: in function `of_unittest':
>>>>> unittest.c:(.init.text+0x120): undefined reference to `of_dma_get_max_cpu_address'
>>
>> Thanks for the report. I think it needs the diff below. If Rob/Nicolas
>> are ok with it, I'll add it to the arm64 tree (with some commit text):
>>
>> diff --git a/drivers/of/unittest.c b/drivers/of/unittest.c
>> index 98cc0163301b..799125ef66fc 100644
>> --- a/drivers/of/unittest.c
>> +++ b/drivers/of/unittest.c
>> @@ -871,6 +871,7 @@ static void __init of_unittest_changeset(void)
>>
>>  static void __init of_unittest_dma_get_max_cpu_address(void)
>>  {
>> +#ifdef CONFIG_OF_ADDRESS
> 
>        if (!IS_ENABLED(CONFIG_OF_ADDRESS))
>                return;
> 
> This once again makes me want to kill off HAS_IOMEM. Or at least
> always have a dummy ioremap() and friends for !HAS_IOMEM.

That would eliminate dozens of build errors on S390 when
# CONFIG_HAS_IOMEM is not set
# CONFIG_OF_ADDRESS is not set

>>         struct device_node *np;
>>         phys_addr_t cpu_addr;
>>
>> @@ -884,6 +885,7 @@ static void __init of_unittest_dma_get_max_cpu_address(void)
>>         unittest(cpu_addr == 0x4fffffff,
>>                  "of_dma_get_max_cpu_address: wrong CPU addr %pad (expecting %x)\n",
>>                  &cpu_addr, 0x4fffffff);
>> +#endif
>>  }
>>
>>  static void __init of_unittest_dma_ranges_one(const char *path,
>>
>> --
>> Catalin
> 


-- 
~Randy

  parent reply	other threads:[~2020-12-01 23:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-01  9:32 [linux-next:master 6272/9613] unittest.c:undefined reference to `of_dma_get_max_cpu_address' kernel test robot
2020-12-01  9:32 ` kernel test robot
2020-12-01 12:29 ` Catalin Marinas
2020-12-01 12:29   ` Catalin Marinas
2020-12-01 12:32   ` Nicolas Saenz Julienne
2020-12-01 12:32     ` Nicolas Saenz Julienne
2020-12-01 20:13   ` Rob Herring
2020-12-01 20:13     ` Rob Herring
2020-12-01 22:28     ` Catalin Marinas
2020-12-01 22:28       ` Catalin Marinas
2020-12-01 23:40     ` Randy Dunlap [this message]
2020-12-01 23:40       ` Randy Dunlap

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=98b2ba67-d43b-c285-8ad0-20e52c1d3227@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=catalin.marinas@arm.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=nsaenzjulienne@suse.de \
    --cc=robh@kernel.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 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.