Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Bharata B Rao <bharata@amd.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 4/4] x86: ibs: Enable IBS profiling for memory accesses
Date: Fri, 7 Mar 2025 20:30:54 +0800	[thread overview]
Message-ID: <202503072051.xg3CbtA0-lkp@intel.com> (raw)
In-Reply-To: <20250306054532.221138-5-bharata@amd.com>

Hi Bharata,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:

[auto build test WARNING on tip/x86/core]
[also build test WARNING on tip/x86/mm linus/master v6.14-rc5]
[cannot apply to akpm-mm/mm-everything next-20250306]
[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#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Bharata-B-Rao/mm-migrate-Allow-misplaced-migration-without-VMA-too/20250306-134949
base:   tip/x86/core
patch link:    https://lore.kernel.org/r/20250306054532.221138-5-bharata%40amd.com
patch subject: [RFC PATCH 4/4] x86: ibs: Enable IBS profiling for memory accesses
config: x86_64-buildonly-randconfig-003-20250307 (https://download.01.org/0day-ci/archive/20250307/202503072051.xg3CbtA0-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250307/202503072051.xg3CbtA0-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202503072051.xg3CbtA0-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> vmlinux.o: warning: objtool: do_syscall_64+0x13: call to hw_access_profiling_stop() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: syscall_enter_from_user_mode_prepare+0x5: call to hw_access_profiling_stop() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: syscall_exit_to_user_mode+0x7b: call to hw_access_profiling_start() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: irqentry_enter_from_user_mode+0x5: call to hw_access_profiling_stop() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: irqentry_exit_to_user_mode+0x71: call to hw_access_profiling_start() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: irqentry_nmi_enter+0x16: call to hw_access_profiling_stop() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: irqentry_nmi_exit+0x22: call to hw_access_profiling_start() leaves .noinstr.text section

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

       reply	other threads:[~2025-03-07 12:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250306054532.221138-5-bharata@amd.com>
2025-03-07 12:30 ` kernel test robot [this message]
2025-03-07 17:56 ` [RFC PATCH 4/4] x86: ibs: Enable IBS profiling for memory accesses kernel test robot

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=202503072051.xg3CbtA0-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bharata@amd.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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