linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
* [mmotm:master 38/317] warning: (MN10300 && ..) selects HAVE_NMI_WATCHDOG which has unmet direct dependencies (HAVE_NMI)
@ 2017-06-17  0:14 kbuild test robot
  2017-06-17  3:06 ` Nicholas Piggin
  0 siblings, 1 reply; 3+ messages in thread
From: kbuild test robot @ 2017-06-17  0:14 UTC (permalink / raw)
  To: Nicholas Piggin
  Cc: kbuild-all, Johannes Weiner, Don Zickus, Babu Moger,
	Andrew Morton, Linux Memory Management List

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

tree:   git://git.cmpxchg.org/linux-mmotm.git master
head:   8c91e2a1ea04c0c1e29415c62f151e77de2291f8
commit: 590b165eb905ab322bb91f04f9708deb8c80f75e [38/317] kernel/watchdog: split up config options
config: mn10300-asb2364_defconfig (attached as .config)
compiler: am33_2.0-linux-gcc (GCC) 6.2.0
reproduce:
        wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout 590b165eb905ab322bb91f04f9708deb8c80f75e
        # save the attached .config to linux build tree
        make.cross ARCH=mn10300 

All warnings (new ones prefixed by >>):

warning: (MN10300 && HAVE_HARDLOCKUP_DETECTOR_ARCH) selects HAVE_NMI_WATCHDOG which has unmet direct dependencies (HAVE_NMI)

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 9358 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [mmotm:master 38/317] warning: (MN10300 && ..) selects HAVE_NMI_WATCHDOG which has unmet direct dependencies (HAVE_NMI)
  2017-06-17  0:14 [mmotm:master 38/317] warning: (MN10300 && ..) selects HAVE_NMI_WATCHDOG which has unmet direct dependencies (HAVE_NMI) kbuild test robot
@ 2017-06-17  3:06 ` Nicholas Piggin
  2017-06-19 14:31   ` Don Zickus
  0 siblings, 1 reply; 3+ messages in thread
From: Nicholas Piggin @ 2017-06-17  3:06 UTC (permalink / raw)
  To: kbuild test robot
  Cc: kbuild-all, Johannes Weiner, Don Zickus, Babu Moger,
	Andrew Morton, Linux Memory Management List

On Sat, 17 Jun 2017 08:14:09 +0800
kbuild test robot <fengguang.wu@intel.com> wrote:

> tree:   git://git.cmpxchg.org/linux-mmotm.git master
> head:   8c91e2a1ea04c0c1e29415c62f151e77de2291f8
> commit: 590b165eb905ab322bb91f04f9708deb8c80f75e [38/317] kernel/watchdog: split up config options
> config: mn10300-asb2364_defconfig (attached as .config)
> compiler: am33_2.0-linux-gcc (GCC) 6.2.0
> reproduce:
>         wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         git checkout 590b165eb905ab322bb91f04f9708deb8c80f75e
>         # save the attached .config to linux build tree
>         make.cross ARCH=mn10300 
> 
> All warnings (new ones prefixed by >>):
> 
> warning: (MN10300 && HAVE_HARDLOCKUP_DETECTOR_ARCH) selects HAVE_NMI_WATCHDOG which has unmet direct dependencies (HAVE_NMI)

Hmm, the arch is not supposed to have HAVE_HARDLOCKUP_DETECTOR_ARCH
without explicitly selecting it. An it does not in the attached .config.
I guess this is Kconfig being helpful...

arch/Kconfig:

config HAVE_NMI_WATCHDOG
        bool
        help
          The arch provides a low level NMI watchdog. It provides
          asm/nmi.h, and defines its own arch_touch_nmi_watchdog().

config HAVE_HARDLOCKUP_DETECTOR_ARCH
        bool
        select HAVE_NMI_WATCHDOG
        help
          The arch chooses to provide its own hardlockup detector, which is
          a superset of the HAVE_NMI_WATCHDOG. It also conforms to config
          interfaces and parameters provided by hardlockup detector subsystem.

Idea was to have arch select HAVE_HARDLOCKUP_DETECTOR_ARCH and it would
get HAVE_NMI_WATCHDOG. Would it be better to make it depend on
HAVE_NMI_WATCHDOG and require the arch select both?

Thanks,
Nick

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [mmotm:master 38/317] warning: (MN10300 && ..) selects HAVE_NMI_WATCHDOG which has unmet direct dependencies (HAVE_NMI)
  2017-06-17  3:06 ` Nicholas Piggin
@ 2017-06-19 14:31   ` Don Zickus
  0 siblings, 0 replies; 3+ messages in thread
From: Don Zickus @ 2017-06-19 14:31 UTC (permalink / raw)
  To: Nicholas Piggin, dhowells
  Cc: kbuild test robot, kbuild-all, Johannes Weiner, Babu Moger,
	Andrew Morton, Linux Memory Management List

(adding David H.)

On Sat, Jun 17, 2017 at 01:06:08PM +1000, Nicholas Piggin wrote:
> On Sat, 17 Jun 2017 08:14:09 +0800
> kbuild test robot <fengguang.wu@intel.com> wrote:
> 
> > tree:   git://git.cmpxchg.org/linux-mmotm.git master
> > head:   8c91e2a1ea04c0c1e29415c62f151e77de2291f8
> > commit: 590b165eb905ab322bb91f04f9708deb8c80f75e [38/317] kernel/watchdog: split up config options
> > config: mn10300-asb2364_defconfig (attached as .config)
> > compiler: am33_2.0-linux-gcc (GCC) 6.2.0
> > reproduce:
> >         wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> >         chmod +x ~/bin/make.cross
> >         git checkout 590b165eb905ab322bb91f04f9708deb8c80f75e
> >         # save the attached .config to linux build tree
> >         make.cross ARCH=mn10300 
> > 
> > All warnings (new ones prefixed by >>):
> > 
> > warning: (MN10300 && HAVE_HARDLOCKUP_DETECTOR_ARCH) selects HAVE_NMI_WATCHDOG which has unmet direct dependencies (HAVE_NMI)

Hmm, MN10300 selects HAVE_NMI_WATCHDOG if MN10300_WD_TIMER is set.  However,
HAVE_NMI_WATCHDOG depends on HAVE_NMI which is not selected for arch
mn10300.  So I am scratching my head how this ever worked, regardless of
this patchset.

Hi David,

Does mn10300 have an NMI entry point (it seemed like you copied an old i386
nmi snapshot during the initial port)?

Cheers,
Don


> 
> Hmm, the arch is not supposed to have HAVE_HARDLOCKUP_DETECTOR_ARCH
> without explicitly selecting it. An it does not in the attached .config.
> I guess this is Kconfig being helpful...
> 
> arch/Kconfig:
> 
> config HAVE_NMI_WATCHDOG
>         bool
>         help
>           The arch provides a low level NMI watchdog. It provides
>           asm/nmi.h, and defines its own arch_touch_nmi_watchdog().
> 
> config HAVE_HARDLOCKUP_DETECTOR_ARCH
>         bool
>         select HAVE_NMI_WATCHDOG
>         help
>           The arch chooses to provide its own hardlockup detector, which is
>           a superset of the HAVE_NMI_WATCHDOG. It also conforms to config
>           interfaces and parameters provided by hardlockup detector subsystem.
> 
> Idea was to have arch select HAVE_HARDLOCKUP_DETECTOR_ARCH and it would
> get HAVE_NMI_WATCHDOG. Would it be better to make it depend on
> HAVE_NMI_WATCHDOG and require the arch select both?
> 
> Thanks,
> Nick

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-06-19 14:31 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-06-17  0:14 [mmotm:master 38/317] warning: (MN10300 && ..) selects HAVE_NMI_WATCHDOG which has unmet direct dependencies (HAVE_NMI) kbuild test robot
2017-06-17  3:06 ` Nicholas Piggin
2017-06-19 14:31   ` Don Zickus

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).