public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Huang, Kai" <kai.huang@intel.com>
To: lkp <lkp@intel.com>
Cc: "oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"Chen, Farrah" <Farrah.Chen@intel.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [kvm:kvm-coco-queue-20250129 43/129] arch/x86/kvm/vmx/main.c:176:13: error: 'vt_exit' undeclared; did you mean 'vmx_exit'?
Date: Fri, 7 Feb 2025 12:09:26 +1300	[thread overview]
Message-ID: <d06757d2-68c4-4ff8-99d9-5da5324ccb36@intel.com> (raw)
In-Reply-To: <202501311811.fRf67aOn-lkp@intel.com>



On 31/01/2025 11:57 pm, lkp wrote:
> tree:   https://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-coco-queue-20250129
> head:   0bc4f452607db4e7eee4d3056cd6ec98636260bc
> commit: 4b55a8f7c5f508fe1dd0005aecc81bbb5676aaec [43/129] KVM: VMX: Refactor VMX module init/exit functions
> config: i386-allmodconfig (https://download.01.org/0day-ci/archive/20250131/202501311811.fRf67aOn-lkp@intel.com/config)
> compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250131/202501311811.fRf67aOn-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/202501311811.fRf67aOn-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
> 
>     In file included from include/linux/kallsyms.h:14,
>                      from include/linux/ftrace.h:13,
>                      from include/linux/kvm_host.h:32,
>                      from arch/x86/kvm/vmx/x86_ops.h:5,
>                      from arch/x86/kvm/vmx/main.c:4:
>     arch/x86/kvm/vmx/main.c: In function '__exittest':
>>> arch/x86/kvm/vmx/main.c:176:13: error: 'vt_exit' undeclared (first use in this function); did you mean 'vmx_exit'?
>       176 | module_exit(vt_exit);

[...]

>     171	static void __vt_exit(void)
>     172	{
>     173		vmx_exit();
>     174		kvm_x86_vendor_exit();
>     175	}
>   > 176	module_exit(vt_exit);
>     177	
> 

The above module_exit(vt_exit) was mistakenly added in the branch 
kvm-coco-queue-20250129, causing this build issue.  There's the second 
module_exit(vt_exit) (the right one) right after this:

+static void __vt_exit(void)
+{
+       vmx_exit();
+       kvm_x86_vendor_exit();
+}
+module_exit(vt_exit);		<--- mistakenly added
+
+static void __exit vt_exit(void)
+{
+       kvm_exit();
+       __vt_exit();
+}
+module_exit(vt_exit);		<--- the right one

The kvm-coco-queue branch doesn't have this issue.




      reply	other threads:[~2025-02-06 23:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-31 10:57 [kvm:kvm-coco-queue-20250129 43/129] arch/x86/kvm/vmx/main.c:176:13: error: 'vt_exit' undeclared; did you mean 'vmx_exit'? kernel test robot
2025-02-06 23:09 ` Huang, Kai [this message]

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=d06757d2-68c4-4ff8-99d9-5da5324ccb36@intel.com \
    --to=kai.huang@intel.com \
    --cc=Farrah.Chen@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pbonzini@redhat.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