From: kernel test robot <lkp@intel.com>
To: Dexuan Cui <decui@microsoft.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [dcui-tdx:decui/tip/tdx/2023/1013 10/10] arch/x86/kernel/x86_init.c:153:32: error: use of undeclared identifier 'print_mem_encrypt_feature_info'
Date: Mon, 23 Oct 2023 05:46:41 +0800 [thread overview]
Message-ID: <202310230519.cdlkHIMz-lkp@intel.com> (raw)
tree: https://github.com/dcui/tdx decui/tip/tdx/2023/1013
head: a1d4d1204a2799ff94c9d1d01f2dda125aafa8e2
commit: a1d4d1204a2799ff94c9d1d01f2dda125aafa8e2 [10/10] x86/mm: Print the encryption features correctly when a paravisor is present
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20231023/202310230519.cdlkHIMz-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231023/202310230519.cdlkHIMz-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/202310230519.cdlkHIMz-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/x86/kernel/x86_init.c:153:32: error: use of undeclared identifier 'print_mem_encrypt_feature_info'
.print_mem_enc_feature_info = print_mem_encrypt_feature_info,
^
1 error generated.
vim +/print_mem_encrypt_feature_info +153 arch/x86/kernel/x86_init.c
139
140 struct x86_platform_ops x86_platform __ro_after_init = {
141 .calibrate_cpu = native_calibrate_cpu_early,
142 .calibrate_tsc = native_calibrate_tsc,
143 .get_wallclock = mach_get_cmos_time,
144 .set_wallclock = mach_set_cmos_time,
145 .iommu_shutdown = iommu_shutdown_noop,
146 .is_untracked_pat_range = is_ISA_range,
147 .nmi_init = default_nmi_init,
148 .get_nmi_reason = default_get_nmi_reason,
149 .save_sched_clock_state = tsc_save_sched_clock_state,
150 .restore_sched_clock_state = tsc_restore_sched_clock_state,
151 .realmode_reserve = reserve_real_mode,
152 .realmode_init = init_real_mode,
> 153 .print_mem_enc_feature_info = print_mem_encrypt_feature_info,
154 .hyper.pin_vcpu = x86_op_int_noop,
155 .hyper.is_private_mmio = is_private_mmio_noop,
156
157 .guest = {
158 .enc_status_change_prepare = enc_status_change_prepare_noop,
159 .enc_status_change_finish = enc_status_change_finish_noop,
160 .enc_tlb_flush_required = enc_tlb_flush_required_noop,
161 .enc_cache_flush_required = enc_cache_flush_required_noop,
162 },
163 };
164
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-10-22 21:47 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=202310230519.cdlkHIMz-lkp@intel.com \
--to=lkp@intel.com \
--cc=decui@microsoft.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.