public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: lkp <lkp@intel.com>, "Yamahata, Isaku" <isaku.yamahata@intel.com>
Cc: "llvm@lists.linux.dev" <llvm@lists.linux.dev>,
	"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>
Subject: Re: [intel-tdx:tdx_kvm_dev-2024-05-30 59/115] arch/x86/kvm/vmx/main.c:224:10: error: call to undeclared function 'tdx_gmem_private_max_mapping_level'; ISO C99 and later do not support implicit function declarations
Date: Fri, 31 May 2024 22:20:59 +0000	[thread overview]
Message-ID: <c51d84cab78bee2bfedcfdd1f4665c77c6e79a67.camel@intel.com> (raw)
In-Reply-To: <202406010133.Yu2O9Air-lkp@intel.com>

On Sat, 2024-06-01 at 02:03 +0800, kernel test robot wrote:
> tree:   https://github.com/intel/tdx.git tdx_kvm_dev-2024-05-30
> head:   538d25a4d08a3dc487fc9be78bef09105ef54e27
> commit: a3c36efd448bd3b25ee0cf2672f177ff603a6be6 [59/115] KVM: TDX: TDP MMU
> TDX support
> config: x86_64-rhel-8.3-rust
> (https://download.01.org/0day-ci/archive/20240601/202406010133.Yu2O9Air-lkp@in
> tel.com/config)
> compiler: clang version 18.1.5
> (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1
> )
> reproduce (this is a W=1 build):
> (https://download.01.org/0day-ci/archive/20240601/202406010133.Yu2O9Air-lkp@in
> tel.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/202406010133.Yu2O9Air-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
> 
> > > arch/x86/kvm/vmx/main.c:224:10: error: call to undeclared function
> > > 'tdx_gmem_private_max_mapping_level'; ISO C99 and later do not support
> > > implicit function declarations [-Wimplicit-function-declaration]
>      224 |                 return tdx_gmem_private_max_mapping_level(kvm,
> pfn);
>          |                        ^
>    arch/x86/kvm/vmx/main.c:224:10: note: did you mean
> 'vt_gmem_private_max_mapping_level'?
>    arch/x86/kvm/vmx/main.c:221:12: note: 'vt_gmem_private_max_mapping_level'
> declared here
>      221 | static int vt_gmem_private_max_mapping_level(struct kvm *kvm,
> kvm_pfn_t pfn)
>          |            ^
>      222 | {
>      223 |         if (is_td(kvm))
>      224 |                 return tdx_gmem_private_max_mapping_level(kvm,
> pfn);
>          |                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>          |                        vt_gmem_private_max_mapping_level
>    1 error generated.

Isaku,

We are just missing a definition for !CONFIG_INTEL_TDX_HOST. I'll just add one
in.

  reply	other threads:[~2024-05-31 22:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31 18:03 [intel-tdx:tdx_kvm_dev-2024-05-30 59/115] arch/x86/kvm/vmx/main.c:224:10: error: call to undeclared function 'tdx_gmem_private_max_mapping_level'; ISO C99 and later do not support implicit function declarations kernel test robot
2024-05-31 22:20 ` Edgecombe, Rick P [this message]
2024-05-31 22:31   ` Yamahata, Isaku

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=c51d84cab78bee2bfedcfdd1f4665c77c6e79a67.camel@intel.com \
    --to=rick.p.edgecombe@intel.com \
    --cc=isaku.yamahata@intel.com \
    --cc=lkp@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox