From: Sean Christopherson <seanjc@google.com>
To: Borislav Petkov <bp@alien8.de>
Cc: kernel test robot <lkp@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
x86@kernel.org
Subject: Re: [tip:x86/alternatives 14/14] arch/x86/kvm/kvm.o: warning: objtool: .altinstr_replacement+0xc5: call without frame pointer save/setup
Date: Mon, 17 Jun 2024 07:39:51 -0700 [thread overview]
Message-ID: <ZnBKtwvvKXXK2b2u@google.com> (raw)
In-Reply-To: <20240615080902.GAZm1MHvXQ30rm1Nnk@fat_crate.local>
On Sat, Jun 15, 2024, Borislav Petkov wrote:
> On Fri, Jun 14, 2024 at 08:35:23AM -0700, Sean Christopherson wrote:
> > > I know Sean had a patchset to cleanup that gunk. Sean?
> >
> > That series was just for the actual VM-Enter/VM-Exit path.
>
> Right, about that. I still see:
>
> vmlinux.o: warning: objtool: svm_vcpu_enter_exit+0xb0: call to sev_es_host_save_area() leaves .noinstr.text section
> vmlinux.o: warning: objtool: svm_vcpu_enter_exit+0xbf: call to sev_es_host_save_area.isra.0() leaves .noinstr.text section
>
> in allyesconfig builds....
Gah, sev_es_host_save_area() needs to be tagged __always_inline.
next prev parent reply other threads:[~2024-06-17 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 8:15 [tip:x86/alternatives 14/14] arch/x86/kvm/kvm.o: warning: objtool: .altinstr_replacement+0xc5: call without frame pointer save/setup kernel test robot
2024-06-14 15:22 ` Borislav Petkov
2024-06-14 15:35 ` Sean Christopherson
2024-06-14 15:58 ` Borislav Petkov
2024-06-15 8:09 ` Borislav Petkov
2024-06-17 14:39 ` Sean Christopherson [this message]
2024-06-18 10:42 ` Peter Zijlstra
2024-06-18 10:47 ` Peter Zijlstra
2024-06-18 20:05 ` [PATCH] x86/alternatives, kvm: Fix a couple of CALLs without a frame pointer Borislav Petkov
2024-06-18 23:19 ` Sean Christopherson
2024-06-18 14:24 ` [tip:x86/alternatives 14/14] arch/x86/kvm/kvm.o: warning: objtool: .altinstr_replacement+0xc5: call without frame pointer save/setup Sean Christopherson
2024-06-18 14:47 ` 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=ZnBKtwvvKXXK2b2u@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--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