All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v2 7/7] arm64: support PREEMPT_DYNAMIC
Date: Sat, 05 Feb 2022 04:41:44 +0800	[thread overview]
Message-ID: <202202050422.iszWUnoX-lkp@intel.com> (raw)
In-Reply-To: <20220204150557.434610-8-mark.rutland@arm.com>

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

Hi Mark,

I love your patch! Yet something to improve:

[auto build test ERROR on tip/sched/core]
[also build test ERROR on v5.17-rc2 next-20220204]
[cannot apply to arm64/for-next/core tip/core/entry]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Mark-Rutland/arm64-sched-preempt-support-PREEMPT_DYNAMIC-with-static-keys/20220204-230707
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git c8eaf6ac76f40f6c59fc7d056e2e08c4a57ea9c7
config: arm64-allyesconfig (https://download.01.org/0day-ci/archive/20220205/202202050422.iszWUnoX-lkp(a)intel.com/config)
compiler: aarch64-linux-gcc (GCC) 11.2.0
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
        # https://github.com/0day-ci/linux/commit/69ea0cc7ce89827b3e08b96bb2181e7efd322b79
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Mark-Rutland/arm64-sched-preempt-support-PREEMPT_DYNAMIC-with-static-keys/20220204-230707
        git checkout 69ea0cc7ce89827b3e08b96bb2181e7efd322b79
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arm64 SHELL=/bin/bash kernel/

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

   In file included from kernel/locking/locktorture.c:30:
   kernel/locking/locktorture.c: In function 'torture_lock_busted_write_delay':
>> include/linux/torture.h:121:36: error: implicit declaration of function 'preempt_schedule'; did you mean 'preempt_schedule_irq'? [-Werror=implicit-function-declaration]
     121 | #define torture_preempt_schedule() preempt_schedule()
         |                                    ^~~~~~~~~~~~~~~~
   kernel/locking/locktorture.c:122:17: note: in expansion of macro 'torture_preempt_schedule'
     122 |                 torture_preempt_schedule();  /* Allow test to be preempted. */
         |                 ^~~~~~~~~~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors
--
   In file included from kernel/rcu/rcutorture.c:42:
   kernel/rcu/rcutorture.c: In function 'rcu_read_delay':
>> include/linux/torture.h:121:36: error: implicit declaration of function 'preempt_schedule'; did you mean 'preempt_schedule_irq'? [-Werror=implicit-function-declaration]
     121 | #define torture_preempt_schedule() preempt_schedule()
         |                                    ^~~~~~~~~~~~~~~~
   kernel/rcu/rcutorture.c:408:17: note: in expansion of macro 'torture_preempt_schedule'
     408 |                 torture_preempt_schedule();  /* QS only if preemptible. */
         |                 ^~~~~~~~~~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors


vim +121 include/linux/torture.h

47cf29b9e72196 Paul E. McKenney 2014-02-03  113  
47cf29b9e72196 Paul E. McKenney 2014-02-03  114  #define torture_create_kthread(n, arg, tp) \
47cf29b9e72196 Paul E. McKenney 2014-02-03  115  	_torture_create_kthread(n, (arg), #n, "Creating " #n " task", \
47cf29b9e72196 Paul E. McKenney 2014-02-03  116  				"Failed to create " #n, &(tp))
9c029b86098dec Paul E. McKenney 2014-02-04  117  #define torture_stop_kthread(n, tp) \
9c029b86098dec Paul E. McKenney 2014-02-04  118  	_torture_stop_kthread("Stopping " #n " task", &(tp))
b5daa8f3b3b2b0 Paul E. McKenney 2014-01-30  119  
01b1d88b09824b Thomas Gleixner  2019-07-26  120  #ifdef CONFIG_PREEMPTION
cc1321c96f8555 Paul E. McKenney 2017-10-16 @121  #define torture_preempt_schedule() preempt_schedule()
cc1321c96f8555 Paul E. McKenney 2017-10-16  122  #else
be44ae62431196 Randy Dunlap     2020-02-25  123  #define torture_preempt_schedule()	do { } while (0)
cc1321c96f8555 Paul E. McKenney 2017-10-16  124  #endif
cc1321c96f8555 Paul E. McKenney 2017-10-16  125  

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

      parent reply	other threads:[~2022-02-04 20:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04 15:05 [PATCH v2 0/7] arm64 / sched/preempt: support PREEMPT_DYNAMIC with static keys Mark Rutland
2022-02-04 15:05 ` Mark Rutland
2022-02-04 15:05 ` [PATCH v2 1/7] sched/preempt: move PREEMPT_DYNAMIC logic later Mark Rutland
2022-02-04 15:05   ` Mark Rutland
2022-02-04 15:05 ` [PATCH v2 2/7] sched/preempt: refactor sched_dynamic_update() Mark Rutland
2022-02-04 15:05   ` Mark Rutland
2022-02-04 15:05 ` [PATCH v2 3/7] sched/preempt: simplify irqentry_exit_cond_resched() callers Mark Rutland
2022-02-04 15:05   ` Mark Rutland
2022-02-04 15:05 ` [PATCH v2 4/7] sched/preempt: decouple HAVE_PREEMPT_DYNAMIC from GENERIC_ENTRY Mark Rutland
2022-02-04 15:05   ` Mark Rutland
2022-02-04 15:05 ` [PATCH v2 5/7] sched/preempt: add PREEMPT_DYNAMIC using static keys Mark Rutland
2022-02-04 15:05   ` Mark Rutland
2022-02-07 11:57   ` Frederic Weisbecker
2022-02-07 11:57     ` Frederic Weisbecker
2022-02-08 12:15     ` Mark Rutland
2022-02-08 12:15       ` Mark Rutland
2022-02-04 15:05 ` [PATCH v2 6/7] arm64: entry: centralize premeption decision Mark Rutland
2022-02-04 15:05   ` Mark Rutland
2022-02-04 18:46   ` Catalin Marinas
2022-02-04 18:46     ` Catalin Marinas
2022-02-04 15:05 ` [PATCH v2 7/7] arm64: support PREEMPT_DYNAMIC Mark Rutland
2022-02-04 15:05   ` Mark Rutland
2022-02-04 18:48   ` Catalin Marinas
2022-02-04 18:48     ` Catalin Marinas
2022-02-04 20:41   ` kernel test robot [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=202202050422.iszWUnoX-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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.