linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>, linux-mm@kvack.org
Cc: kbuild-all@lists.01.org, akpm@linux-foundation.org,
	naoya.horiguchi@linux.dev, rostedt@goodmis.org,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	Ingo Molnar <mingo@redhat.com>, Zi Yan <ziy@nvidia.com>,
	Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
	John Hubbard <jhubbard@nvidia.com>,
	Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH V2 2/2] mm/migration: Add trace events for base page and HugeTLB migrations
Date: Tue, 25 Jan 2022 19:13:53 +0800	[thread overview]
Message-ID: <202201251948.RMGoyUiL-lkp@intel.com> (raw)
In-Reply-To: <1643080105-11416-3-git-send-email-anshuman.khandual@arm.com>

Hi Anshuman,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on v5.17-rc1]
[also build test ERROR on next-20220124]
[cannot apply to hnaz-mm/master rostedt-trace/for-next]
[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/Anshuman-Khandual/mm-migration-Add-trace-events/20220125-110944
base:    e783362eb54cd99b2cac8b3a9aeac942e6f6ac07
config: i386-randconfig-a012-20211214 (https://download.01.org/0day-ci/archive/20220125/202201251948.RMGoyUiL-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://github.com/0day-ci/linux/commit/f1100840c009fceb20d26ac4564c9d4c9c23c729
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Anshuman-Khandual/mm-migration-Add-trace-events/20220125-110944
        git checkout f1100840c009fceb20d26ac4564c9d4c9c23c729
        # save the config file to linux build tree
        mkdir build_dir
        make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash

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

   ld: mm/rmap.o: in function `arch_atomic_read':
>> arch/x86/include/asm/atomic.h:29: undefined reference to `__tracepoint_set_migration_pte'
   ld: mm/rmap.o: in function `trace_set_migration_pte':
   include/trace/events/migrate.h:129: undefined reference to `__tracepoint_set_migration_pte'
   ld: include/trace/events/migrate.h:129: undefined reference to `__tracepoint_set_migration_pte'
   ld: include/trace/events/migrate.h:129: undefined reference to `__SCT__tp_func_set_migration_pte'


vim +29 arch/x86/include/asm/atomic.h

5abbbbf0b0cd4a Brian Gerst    2010-01-07  11  
5abbbbf0b0cd4a Brian Gerst    2010-01-07  12  /*
5abbbbf0b0cd4a Brian Gerst    2010-01-07  13   * Atomic operations that C can't guarantee us.  Useful for
5abbbbf0b0cd4a Brian Gerst    2010-01-07  14   * resource counting etc..
5abbbbf0b0cd4a Brian Gerst    2010-01-07  15   */
5abbbbf0b0cd4a Brian Gerst    2010-01-07  16  
5abbbbf0b0cd4a Brian Gerst    2010-01-07  17  /**
8bf705d130396e Dmitry Vyukov  2018-01-29  18   * arch_atomic_read - read atomic variable
5abbbbf0b0cd4a Brian Gerst    2010-01-07  19   * @v: pointer of type atomic_t
5abbbbf0b0cd4a Brian Gerst    2010-01-07  20   *
5abbbbf0b0cd4a Brian Gerst    2010-01-07  21   * Atomically reads the value of @v.
5abbbbf0b0cd4a Brian Gerst    2010-01-07  22   */
8bf705d130396e Dmitry Vyukov  2018-01-29  23  static __always_inline int arch_atomic_read(const atomic_t *v)
5abbbbf0b0cd4a Brian Gerst    2010-01-07  24  {
ac605bee0bfab4 Dmitry Vyukov  2018-01-29  25  	/*
ac605bee0bfab4 Dmitry Vyukov  2018-01-29  26  	 * Note for KASAN: we deliberately don't use READ_ONCE_NOCHECK() here,
ac605bee0bfab4 Dmitry Vyukov  2018-01-29  27  	 * it's non-inlined function that increases binary size and stack usage.
ac605bee0bfab4 Dmitry Vyukov  2018-01-29  28  	 */
37f8173dd84936 Peter Zijlstra 2020-01-24 @29  	return __READ_ONCE((v)->counter);
5abbbbf0b0cd4a Brian Gerst    2010-01-07  30  }
5abbbbf0b0cd4a Brian Gerst    2010-01-07  31  

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


  parent reply	other threads:[~2022-01-25 11:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25  3:08 [PATCH V2 0/2] mm/migration: Add trace events Anshuman Khandual
2022-01-25  3:08 ` [PATCH V2 1/2] mm/migration: Add trace events for THP migrations Anshuman Khandual
2022-01-25  3:08 ` [PATCH V2 2/2] mm/migration: Add trace events for base page and HugeTLB migrations Anshuman Khandual
2022-01-25  9:41   ` kernel test robot
2022-01-25  9:41   ` kernel test robot
2022-01-25 10:28     ` Anshuman Khandual
2022-01-27  4:07       ` Andrew Morton
2022-01-27  4:52         ` Anshuman Khandual
2022-01-27  6:55           ` Anshuman Khandual
2022-01-25 11:13   ` kernel test robot [this message]
2022-01-25 13:28   ` Matthew Wilcox
2022-01-25 15:16     ` Steven Rostedt

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=202201251948.RMGoyUiL-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=jhubbard@nvidia.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=naoya.horiguchi@linux.dev \
    --cc=rostedt@goodmis.org \
    --cc=willy@infradead.org \
    --cc=ziy@nvidia.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).