From: kernel test robot <lkp@intel.com>
To: Zhiming Hu <zhiming.hu@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
kvm@vger.kernel.org, Farrah Chen <farrah.chen@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Isaku Yamahata <isaku.yamahata@intel.com>
Subject: [kvm:kvm-coco-queue 30/121] arch/x86/include/asm/tdx.h:183:12: error: unused function 'tdx_get_nr_guest_keyids'
Date: Mon, 24 Feb 2025 07:39:35 +0800 [thread overview]
Message-ID: <202502240742.C79LoViU-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-coco-queue
head: ff2046f9bcd0883c72158404a1466eb96781ccca
commit: 5c017bb4d89f65807c56d652443b53e7765b8b35 [30/121] KVM: TDX: Register TDX host key IDs to cgroup misc controller
config: x86_64-randconfig-004-20250224 (https://download.01.org/0day-ci/archive/20250224/202502240742.C79LoViU-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250224/202502240742.C79LoViU-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/202502240742.C79LoViU-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from <built-in>:4:
In file included from drivers/gpu/drm/xe/compat-i915-headers/i915_utils.h:6:
In file included from drivers/gpu/drm/xe/compat-i915-headers/../../i915/i915_utils.h:37:
In file included from arch/x86/include/asm/hypervisor.h:37:
In file included from arch/x86/include/asm/kvm_para.h:10:
>> arch/x86/include/asm/tdx.h:183:12: error: unused function 'tdx_get_nr_guest_keyids' [-Werror,-Wunused-function]
183 | static u32 tdx_get_nr_guest_keyids(void) { return 0; }
| ^~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for FB_IOMEM_HELPERS
Depends on [n]: HAS_IOMEM [=y] && FB_CORE [=n]
Selected by [m]:
- DRM_XE_DISPLAY [=y] && HAS_IOMEM [=y] && DRM [=m] && DRM_XE [=m] && DRM_XE [=m]=m [=m] && HAS_IOPORT [=y]
vim +/tdx_get_nr_guest_keyids +183 arch/x86/include/asm/tdx.h
162
163 u64 tdh_mng_addcx(struct tdx_td *td, struct page *tdcs_page);
164 u64 tdh_vp_addcx(struct tdx_vp *vp, struct page *tdcx_page);
165 u64 tdh_mng_key_config(struct tdx_td *td);
166 u64 tdh_mng_create(struct tdx_td *td, u16 hkid);
167 u64 tdh_vp_create(struct tdx_td *td, struct tdx_vp *vp);
168 u64 tdh_mng_rd(struct tdx_td *td, u64 field, u64 *data);
169 u64 tdh_vp_flush(struct tdx_vp *vp);
170 u64 tdh_mng_vpflushdone(struct tdx_td *td);
171 u64 tdh_mng_key_freeid(struct tdx_td *td);
172 u64 tdh_mng_init(struct tdx_td *td, u64 td_params, u64 *extended_err);
173 u64 tdh_vp_init(struct tdx_vp *vp, u64 initial_rcx, u32 x2apicid);
174 u64 tdh_vp_rd(struct tdx_vp *vp, u64 field, u64 *data);
175 u64 tdh_vp_wr(struct tdx_vp *vp, u64 field, u64 data, u64 mask);
176 u64 tdh_phymem_page_reclaim(struct page *page, u64 *tdx_pt, u64 *tdx_owner, u64 *tdx_size);
177 u64 tdh_phymem_cache_wb(bool resume);
178 u64 tdh_phymem_page_wbinvd_tdr(struct tdx_td *td);
179 #else
180 static inline void tdx_init(void) { }
181 static inline int tdx_cpu_enable(void) { return -ENODEV; }
182 static inline int tdx_enable(void) { return -ENODEV; }
> 183 static u32 tdx_get_nr_guest_keyids(void) { return 0; }
184 static inline const char *tdx_dump_mce_info(struct mce *m) { return NULL; }
185 static inline const struct tdx_sys_info *tdx_get_sysinfo(void) { return NULL; }
186 #endif /* CONFIG_INTEL_TDX_HOST */
187
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-23 23:39 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=202502240742.C79LoViU-lkp@intel.com \
--to=lkp@intel.com \
--cc=farrah.chen@intel.com \
--cc=isaku.yamahata@intel.com \
--cc=kvm@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pbonzini@redhat.com \
--cc=zhiming.hu@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