From: kernel test robot <lkp@intel.com>
To: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>, Tony Luck <tony.luck@intel.com>
Subject: [intel-tdx:guest-upstream 15/38] arch/x86/kernel/process.o: warning: objtool: .altinstr_replacement+0x5: call without frame pointer save/setup
Date: Wed, 24 Nov 2021 03:06:04 +0800 [thread overview]
Message-ID: <202111240211.wdrjK2u4-lkp@intel.com> (raw)
tree: https://github.com/intel/tdx.git guest-upstream
head: 6de233e56ad1ba06ef0bbe20a9377c47f49e6366
commit: e565a4318c87e3d1243bb31b89c53aff081472c5 [15/38] x86/tdx: Add HLT support for TDX guests
config: x86_64-randconfig-a001-20211123 (https://download.01.org/0day-ci/archive/20211124/202111240211.wdrjK2u4-lkp@intel.com/config.gz)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/intel/tdx/commit/e565a4318c87e3d1243bb31b89c53aff081472c5
git remote add intel-tdx https://github.com/intel/tdx.git
git fetch --no-tags intel-tdx guest-upstream
git checkout e565a4318c87e3d1243bb31b89c53aff081472c5
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash arch/x86/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/x86/kernel/process.o: warning: objtool: .altinstr_replacement+0x5: call without frame pointer save/setup
arch/x86/kernel/process.o: warning: objtool: .altinstr_replacement+0x0: call without frame pointer save/setup
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-11-23 19:06 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=202111240211.wdrjK2u4-lkp@intel.com \
--to=lkp@intel.com \
--cc=ak@linux.intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=tony.luck@intel.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).