All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Sean Christopherson <seanjc@google.com>, Mark Brown <broonie@kernel.org>
Cc: Chao Gao <chao.gao@intel.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Vishal Verma <vishal.l.verma@intel.com>
Subject: Re: linux-next: manual merge of the kvm-x86 tree with the tip tree
Date: Thu, 5 Mar 2026 12:24:01 -0700	[thread overview]
Message-ID: <20260305192401.GA1783111@ax162> (raw)
In-Reply-To: <aai71uI977FU6599@google.com>

On Wed, Mar 04, 2026 at 03:10:14PM -0800, Sean Christopherson wrote:
> On Wed, Mar 04, 2026, Mark Brown wrote:
> > Hi all,
> > 
> > Today's linux-next merge of the kvm-x86 tree got a conflict in:
> > 
> >   arch/x86/virt/vmx/tdx/tdx_global_metadata.c
> > 
> > between commit:
> > 
> >   311214bf1df4b ("x86/virt/tdx: Retrieve TDX module version")
> > 
> > from the tip tree and commit:
> > 
> >   75b6c694eaed4 ("x86/virt/tdx: Tag a pile of functions as __init, and globals as __ro_after_init")
> > 
> > from the kvm-x86 tree.
> > 
> > I fixed it up (see below) and can carry the fix as necessary. This
> > is now fixed as far as linux-next is concerned, but any non trivial
> > conflicts should be mentioned to your upstream maintainer when your tree
> > is submitted for merging.  You may also want to consider cooperating
> > with the maintainer of the conflicting tree to minimise any particularly
> > complex conflicts.
> > 
> > diff --cc arch/x86/virt/vmx/tdx/tdx_global_metadata.c
> > index 4c9917a9c2c39,360963bc9328f..0000000000000
> > --- a/arch/x86/virt/vmx/tdx/tdx_global_metadata.c
> > +++ b/arch/x86/virt/vmx/tdx/tdx_global_metadata.c
> > @@@ -7,22 -7,7 +7,22 @@@
> >    * Include this file to other C file instead.
> >    */
> >   
> >  +static int get_tdx_sys_info_version(struct tdx_sys_info_version *sysinfo_version)
> 
> Functionally this is a-ok, but we should remember to mention to Linus (and Paolo)
> that this can be marked __init when the two branches get smushed together.

s/can be/need to be/, I am seeing warnings from modpost as a result of
get_tdx_sys_info_version() lacking __init when building with clang:

  $ make -skj"$(nproc)" ARCH=x86_64 LLVM=1 mrproper allmodconfig all
  ...
  WARNING: modpost: vmlinux: section mismatch in reference: get_tdx_sys_info_version+0x3e (section: .text.unlikely.) -> read_sys_metadata_field (section: .init.text)
  WARNING: modpost: vmlinux: section mismatch in reference: get_tdx_sys_info_version+0x90 (section: .text.unlikely.) -> read_sys_metadata_field (section: .init.text)
  WARNING: modpost: vmlinux: section mismatch in reference: get_tdx_sys_info_version+0xc0 (section: .text.unlikely.) -> read_sys_metadata_field (section: .init.text)

This obviously clears it. Mark, can that be applied to whichever merge
happens second?

Cheers,
Nathan

diff --git a/arch/x86/virt/vmx/tdx/tdx_global_metadata.c b/arch/x86/virt/vmx/tdx/tdx_global_metadata.c
index e854aa0ca649..c7db393a9cfb 100644
--- a/arch/x86/virt/vmx/tdx/tdx_global_metadata.c
+++ b/arch/x86/virt/vmx/tdx/tdx_global_metadata.c
@@ -7,7 +7,7 @@
  * Include this file to other C file instead.
  */
 
-static int get_tdx_sys_info_version(struct tdx_sys_info_version *sysinfo_version)
+static __init int get_tdx_sys_info_version(struct tdx_sys_info_version *sysinfo_version)
 {
 	int ret = 0;
 	u64 val;

  reply	other threads:[~2026-03-05 19:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04 12:21 linux-next: manual merge of the kvm-x86 tree with the tip tree Mark Brown
2026-03-04 23:10 ` Sean Christopherson
2026-03-05 19:24   ` Nathan Chancellor [this message]
2026-03-06 13:24     ` Mark Brown
2026-03-06 22:48       ` Nathan Chancellor
  -- strict thread matches above, loose matches on Subject: below --
2025-11-25  4:59 Stephen Rothwell
2025-11-25  7:09 ` Borislav Petkov
2025-12-04  5:10 ` Stephen Rothwell
2025-11-20  4:52 Stephen Rothwell
2025-11-20  4:46 Stephen Rothwell
2025-10-20  0:07 Stephen Rothwell
2025-09-22  9:50 Mark Brown
2025-09-22 11:27 ` Aithal, Srikanth
2025-09-22 11:40   ` Mark Brown
2025-09-22 13:23     ` Mark Brown
2025-09-22 14:04     ` Sean Christopherson
2025-09-30 18:13 ` Paolo Bonzini
2025-09-19 13:50 Mark Brown
2025-01-06  4:05 Stephen Rothwell
2025-01-09 19:18 ` Sean Christopherson
2025-01-23  3:25 ` Stephen Rothwell
2024-02-07  4:35 Stephen Rothwell
2023-01-19 23:54 Stephen Rothwell

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=20260305192401.GA1783111@ax162 \
    --to=nathan@kernel.org \
    --cc=broonie@kernel.org \
    --cc=chao.gao@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=seanjc@google.com \
    --cc=vishal.l.verma@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 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.