From: Randy Dunlap <rdunlap@infradead•org>
To: Josh Poimboeuf <jpoimboe@redhat•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Peter Zijlstra <peterz@infradead•org>
Subject: Re: linux-next: Tree for Apr 20 (objtool warning)
Date: Mon, 20 Apr 2020 09:14:05 -0700 [thread overview]
Message-ID: <96be5a96-07f6-7343-e159-ffb110646d76@infradead.org> (raw)
In-Reply-To: <20200420155330.5uepjeyfsso5l4rm@treble>
On 4/20/20 8:53 AM, Josh Poimboeuf wrote:
> On Mon, Apr 20, 2020 at 08:29:04AM -0700, Randy Dunlap wrote:
>> On 4/19/20 9:26 PM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20200417:
>>>
>>
>> on x86_64:
>>
>> arch/x86/kvm/svm/vmenter.o: warning: objtool: __svm_vcpu_run()+0xe4: BP used as a scratch register
>>
>> Full randconfig file is included.
>
> Yeah, frame pointers are toast in that function. We'll need something
> like:
That works for me. Thanks.
Acked-by: Randy Dunlap <rdunlap@infradead•org>
> diff --git a/arch/x86/kvm/Makefile b/arch/x86/kvm/Makefile
> index a789759b7261..221e2bd7e76d 100644
> --- a/arch/x86/kvm/Makefile
> +++ b/arch/x86/kvm/Makefile
> @@ -3,6 +3,10 @@
> ccflags-y += -Iarch/x86/kvm
> ccflags-$(CONFIG_KVM_WERROR) += -Werror
>
> +ifeq ($(CONFIG_UNWINDER_FRAME_POINTER),y)
> +OBJECT_FILES_NON_STANDARD_vmenter.o := y
> +endif
> +
> KVM := ../../../virt/kvm
>
> kvm-y += $(KVM)/kvm_main.o $(KVM)/coalesced_mmio.o \
>
>
--
~Randy
next prev parent reply other threads:[~2020-04-20 16:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 4:26 linux-next: Tree for Apr 20 Stephen Rothwell
2020-04-20 7:14 ` Christian Borntraeger
2020-04-20 7:23 ` Hadar Gat
2020-04-20 7:30 ` Christian Borntraeger
2020-04-20 7:25 ` Stephen Rothwell
2020-04-20 15:21 ` linux-next: Tree for Apr 20 (media Kconfig warning) Randy Dunlap
2020-04-20 15:45 ` Randy Dunlap
2020-04-20 15:29 ` linux-next: Tree for Apr 20 (objtool warning) Randy Dunlap
2020-04-20 15:53 ` Josh Poimboeuf
2020-04-20 16:14 ` Randy Dunlap [this message]
2020-04-20 16:33 ` linux-next: Tree for Apr 20 (media: usbvision) Randy Dunlap
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=96be5a96-07f6-7343-e159-ffb110646d76@infradead.org \
--to=rdunlap@infradead$(echo .)org \
--cc=jpoimboe@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=peterz@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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