Received-SPF: pass (google.com: domain of linux-kernel+bounces-166014-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Date: Thu, 2 May 2024 16:47:11 +1000
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Paolo Bonzini <pbonzini@redhat.com>, Thomas Gleixner
 <tglx@linutronix.de>, Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin"
 <hpa@zytor.com>, Peter Zijlstra <peterz@infradead.org>
Cc: Jacob Pan <jacob.jun.pan@linux.intel.com>, Isaku Yamahata
 <isaku.yamahata@intel.com>, Sean Christopherson <seanjc@google.com>,
 Xiaoyao Li <xiaoyao.li@intel.com>, KVM <kvm@vger.kernel.org>, Linux Kernel
 Mailing List <linux-kernel@vger.kernel.org>, Linux Next Mailing List
 <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the kvm tree
Message-ID: <20240502164711.06b5aca6@canb.auug.org.au>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/u9taxsfNaih2JgKfzbuTXpf";
 protocol="application/pgp-signature"; micalg=pgp-sha256

--Sig_/u9taxsfNaih2JgKfzbuTXpf
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi all,

After merging the kvm tree, today's linux-next build (x86_64 allmodconfig)
failed like this:

arch/x86/kvm/vmx/main.c:102:43: error: 'pi_has_pending_interrupt' undeclare=
d here (not in a function)
  102 |         .dy_apicv_has_pending_interrupt =3D pi_has_pending_interrup=
t,
      |                                           ^~~~~~~~~~~~~~~~~~~~~~~~
arch/x86/kvm/vmx/main.c:131:27: error: 'vmx_pi_update_irte' undeclared here=
 (not in a function); did you mean 'kvm_apic_update_irr'?
  131 |         .pi_update_irte =3D vmx_pi_update_irte,
      |                           ^~~~~~~~~~~~~~~~~~
      |                           kvm_apic_update_irr
arch/x86/kvm/vmx/main.c:132:32: error: 'vmx_pi_start_assignment' undeclared=
 here (not in a function); did you mean 'kvm_arch_start_assignment'?
  132 |         .pi_start_assignment =3D vmx_pi_start_assignment,
      |                                ^~~~~~~~~~~~~~~~~~~~~~~
      |                                kvm_arch_start_assignment

Probably caused by commit

  5f18c642ff7e ("KVM: VMX: Move out vmx_x86_ops to 'main.c' to dispatch VMX=
 and TDX")

interacting with commit

  699f67512f04 ("KVM: VMX: Move posted interrupt descriptor out of VMX code=
")

from the tip tree.

I have applied the following merge resolution patch.

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Thu, 2 May 2024 14:13:25 +1000
Subject: [PATCH] fixup for "KVM: VMX: Move posted interrupt descriptor out =
of
 VMX code"

interacting with commit

  5f18c642ff7e ("KVM: VMX: Move out vmx_x86_ops to 'main.c' to dispatch VMX=
 andTDX")

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 arch/x86/kvm/vmx/main.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/x86/kvm/vmx/main.c b/arch/x86/kvm/vmx/main.c
index 7c546ad3e4c9..d4ed681785fd 100644
--- a/arch/x86/kvm/vmx/main.c
+++ b/arch/x86/kvm/vmx/main.c
@@ -5,6 +5,7 @@
 #include "vmx.h"
 #include "nested.h"
 #include "pmu.h"
+#include "posted_intr.h"
=20
 #define VMX_REQUIRED_APICV_INHIBITS				\
 	(BIT(APICV_INHIBIT_REASON_DISABLE)|			\
--=20
2.43.0

--=20
Cheers,
Stephen Rothwell

--Sig_/u9taxsfNaih2JgKfzbuTXpf
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmYzNu8ACgkQAVBC80lX
0GzQeAf/QqH2Kd0FrILfzRcfD/fuGeTiiQhbezCcAffbBJ0B74DONLWlg1Zi/UAz
4LyeaRA6E8FrL2/wfTe+XTazFuB9hzWxvEr+sPbwPBwtjQdk+c/0/JlQ1ZLhbT3T
t2k/xkPQEIZm5s9y37RjemCVvLICSdcr5FnJBKnR8SBwH4U6TqE+g5GYmAIVdDhC
29t9Ileob+8btzcIRbP/13JYnSQBfgkQqJbT2Ff4Q/CVdYCP/HdICm5KHuXUzMD6
rHlKsHynE91+zOSwOnFei/PZuC2Qte/lwddcK9Xi8OebO9kRv1cUNu64whVRx3iN
E7TDTmPlXwsXo5YRpVSd16d+uG3K7A==
=HXEM
-----END PGP SIGNATURE-----

--Sig_/u9taxsfNaih2JgKfzbuTXpf--