From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "eadavis@qq.com" <eadavis@qq.com>,
"binbin.wu@linux.intel.com" <binbin.wu@linux.intel.com>
Cc: "seanjc@google.com" <seanjc@google.com>,
"bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH next V2] KVM: VMX: use __always_inline for is_td_vcpu and is_td
Date: Tue, 27 May 2025 17:53:50 +0000 [thread overview]
Message-ID: <c281170eeeda8974eb0e0f755b55c998ba01b7a2.camel@intel.com> (raw)
In-Reply-To: <tencent_1A767567C83C1137829622362E4A72756F09@qq.com>
On Tue, 2025-05-27 at 16:44 +0800, Edward Adam Davis wrote:
> is_td() and is_td_vcpu() run in no instrumentation, so use __always_inline
> to replace inline.
>
> [1]
> vmlinux.o: error: objtool: vmx_handle_nmi+0x47:
> call to is_td_vcpu.isra.0() leaves .noinstr.text section
>
> Fixes: 7172c753c26a ("KVM: VMX: Move common fields of struct vcpu_{vmx,tdx} to a struct")
> Signed-off-by: Edward Adam Davis <eadavis@qq.com>
> ---
> V1 -> V2: using __always_inline to replace noinstr
Argh, for some reason the original report was sent just to Paolo and so I didn't
see this until now:
https://lore.kernel.org/oe-kbuild-all/202505071640.fUgzT6SF-lkp@intel.com/
You (or Paolo) might want to add that link for [1]. Fix looks good.
Tested-by: Rick Edgecombe <rick.p.edgecombe@intel.com>
next prev parent reply other threads:[~2025-05-27 17:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 3:45 [PATCH next] KVM: VMX: add noinstr " Edward Adam Davis
2025-05-27 5:31 ` Binbin Wu
2025-05-27 5:39 ` Edward Adam Davis
2025-05-27 8:44 ` [PATCH next V2] KVM: VMX: use __always_inline " Edward Adam Davis
2025-05-27 11:07 ` Peter Zijlstra
2025-05-27 12:34 ` Huang, Kai
2025-05-27 13:47 ` Peter Zijlstra
2025-05-27 21:47 ` Huang, Kai
2025-05-27 17:53 ` Edgecombe, Rick P [this message]
2025-05-27 21:48 ` Huang, Kai
2025-05-28 0:28 ` Binbin Wu
2025-05-27 8:28 ` [PATCH next] KVM: VMX: add noinstr " kernel test robot
2025-05-27 11:07 ` Peter Zijlstra
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=c281170eeeda8974eb0e0f755b55c998ba01b7a2.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=binbin.wu@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=eadavis@qq.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®