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: Sat, 8 Mar 2025 01:56:25 +0800 [thread overview]
Message-ID: <202503080104.AHMWmR7w-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-20250307]
[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-005-20250307 (https://download.01.org/0day-ci/archive/20250308/202503080104.AHMWmR7w-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/20250308/202503080104.AHMWmR7w-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/202503080104.AHMWmR7w-lkp@intel.com/
All warnings (new ones prefixed by >>):
vmlinux.o: warning: objtool: do_syscall_64+0x11: call to hw_access_profiling_stop() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: do_int80_emulation+0x16: 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+0xcc: 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+0xc2: call to hw_access_profiling_start() leaves .noinstr.text section
vmlinux.o: warning: objtool: irqentry_nmi_enter+0x1c: call to hw_access_profiling_stop() leaves .noinstr.text section
vmlinux.o: warning: objtool: irqentry_nmi_exit+0x63: call to hw_access_profiling_start() leaves .noinstr.text section
vmlinux.o: warning: objtool: ia32_setup_rt_frame+0x135: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: compat_get_bitmap+0xb3: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: compat_put_bitmap+0xb3: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: __sanitizer_cov_trace_cmp1+0xd: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: __sanitizer_cov_trace_cmp2+0x10: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: __sanitizer_cov_trace_cmp4+0x10: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: __sanitizer_cov_trace_cmp8+0xf: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: __sanitizer_cov_trace_const_cmp1+0x10: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: __sanitizer_cov_trace_const_cmp2+0x10: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: __sanitizer_cov_trace_const_cmp4+0x10: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: __sanitizer_cov_trace_const_cmp8+0xf: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: __sanitizer_cov_trace_switch+0x51: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: fault_in_writeable+0xae: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: fault_in_readable+0xb5: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: fillonedir+0x179: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: filldir+0x245: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: filldir64+0x244: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: compat_fillonedir+0x1ae: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: compat_filldir+0x28e: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: copy_iovec_from_user+0x98: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: check_zeroed_user+0xce: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: strncpy_from_user+0x8a: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: strnlen_user+0xa7: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
vmlinux.o: warning: objtool: copy_mc_fragile_handle_tail+0x4d: call to write_comp_data.llvm.15977173092665352742() with UACCESS enabled
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-03-07 17:56 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 5:45 [RFC PATCH 0/4] Kernel daemon for detecting and promoting hot pages Bharata B Rao
2025-03-06 5:45 ` [RFC PATCH 1/4] mm: migrate: Allow misplaced migration without VMA too Bharata B Rao
2025-03-06 12:13 ` David Hildenbrand
2025-03-07 3:00 ` Bharata B Rao
2025-03-06 17:24 ` Gregory Price
2025-03-06 17:45 ` Matthew Wilcox
2025-03-06 18:19 ` Gregory Price
2025-03-06 18:42 ` Matthew Wilcox
2025-03-06 20:03 ` Gregory Price
2025-03-24 2:55 ` Balbir Singh
2025-03-24 14:51 ` Bharata B Rao
2025-03-06 5:45 ` [RFC PATCH 2/4] mm: kpromoted: Hot page info collection and promotion daemon Bharata B Rao
2025-03-06 17:22 ` Mike Day
2025-03-07 3:27 ` Bharata B Rao
2025-03-07 7:23 ` kernel test robot
2025-03-13 16:44 ` Davidlohr Bueso
2025-03-17 3:39 ` Bharata B Rao
2025-03-17 15:05 ` Gregory Price
2025-03-17 16:22 ` Bharata B Rao
2025-03-17 18:24 ` Gregory Price
2025-03-13 20:36 ` Davidlohr Bueso
2025-03-17 3:49 ` Bharata B Rao
2025-03-14 15:28 ` Jonathan Cameron
2025-03-18 4:09 ` Bharata B Rao
2025-03-18 14:17 ` Jonathan Cameron
2025-03-24 3:35 ` Balbir Singh
2025-03-28 4:55 ` Bharata B Rao
2025-03-24 13:43 ` Gregory Price
2025-03-24 14:34 ` Bharata B Rao
2025-03-06 5:45 ` [RFC PATCH 3/4] x86: ibs: In-kernel IBS driver for memory access profiling Bharata B Rao
2025-03-14 15:38 ` Jonathan Cameron
2025-03-06 5:45 ` [RFC PATCH 4/4] x86: ibs: Enable IBS profiling for memory accesses Bharata B Rao
2025-03-07 12:30 ` kernel test robot
2025-03-07 17:56 ` kernel test robot [this message]
2025-03-16 22:00 ` [RFC PATCH 0/4] Kernel daemon for detecting and promoting hot pages SeongJae Park
2025-03-18 6:33 ` Raghavendra K T
2025-03-18 10:45 ` Bharata B Rao
2025-03-18 5:28 ` Balbir Singh
2025-03-20 9:07 ` Bharata B Rao
2025-03-21 6:19 ` Balbir Singh
2025-03-25 8:18 ` Bharata B Rao
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=202503080104.AHMWmR7w-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 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.