From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [peterz-queue:call-depth-tracking 34/60] arch/x86/lib/copy_page_64.o: warning: objtool: .altinstr_replacement(): can't find starting instruction
Date: Fri, 23 Sep 2022 23:21:27 +0800 [thread overview]
Message-ID: <202209232315.eRwoBhq2-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git call-depth-tracking
head: 856304fc062b9ad34742a604b98cc775846c0cb3
commit: c2a8b8187418956af92d2d954ee4574f87f5e188 [34/60] objtool: Rework instruction -> symbol mapping
config: x86_64-defconfig (https://download.01.org/0day-ci/archive/20220923/202209232315.eRwoBhq2-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-5) 11.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git/commit/?id=c2a8b8187418956af92d2d954ee4574f87f5e188
git remote add peterz-queue https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git
git fetch --no-tags peterz-queue call-depth-tracking
git checkout c2a8b8187418956af92d2d954ee4574f87f5e188
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/x86/lib/copy_page_64.o: warning: objtool: .altinstr_replacement(): can't find starting instruction
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-09-23 15:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202209232315.eRwoBhq2-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®