From: Peter Zijlstra <peterz@infradead.org>
To: Sean Christopherson <seanjc@google.com>
Cc: Borislav Petkov <bp@alien8.de>, kernel test robot <lkp@intel.com>,
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: Tue, 18 Jun 2024 16:47:24 +0200 [thread overview]
Message-ID: <20240618144724.GG31592@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <ZnGYsdiOYjLJBX1n@google.com>
On Tue, Jun 18, 2024 at 07:24:49AM -0700, Sean Christopherson wrote:
> On Tue, Jun 18, 2024, Peter Zijlstra wrote:
> > Also, notably, this patch:
> >
> > https://lkml.kernel.org/r/20231204093732.323101886@infradead.org
> >
> > cures things.
>
> Speaking of that series, do you need/want any help pushing it along? I ran into
> build issues[*] and didn't have the cycles to fully figure things out at the time.
Right, saw that. Life caught up with me for a bit and now I'm struggling
with this giant backlog of things.
That is to say, if you have cycles for this, then please. Otherwise,
I'll get to it eventually.
prev parent reply other threads:[~2024-06-18 14:47 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
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 [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=20240618144724.GG31592@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--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=seanjc@google.com \
--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