[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20211123162137.3a8b729f@canb.auug.org.au>
Date: Tue, 23 Nov 2021 16:21:37 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
"H. Peter Anvin" <hpa@...or.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the tip tree
Hi all,
On Fri, 17 Sep 2021 10:23:48 +0200 Peter Zijlstra <peterz@...radead.org> wrote:
>
> On Fri, Sep 17, 2021 at 11:58:59AM +1000, Stephen Rothwell wrote:
> >
> > After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> > produced this warning:
> >
> > vmlinux.o: warning: objtool: mce_setup()+0x22: call to memset() leaves .noinstr.text section
> > vmlinux.o: warning: objtool: do_machine_check()+0x51: call to mce_gather_info() leaves .noinstr.text section
>
> Those are pre-existing and Boris is lokoing into them
I am still seeing the above 2 warnings and also now:
vmlinux.o: warning: objtool: xen_get_debugreg()+0xb: call to HYPERVISOR_get_debugreg() leaves .noinstr.text section
vmlinux.o: warning: objtool: xen_set_debugreg()+0x15: call to HYPERVISOR_set_debugreg.isra.0() leaves .noinstr.text section
Presumably caused by
f4afb713e5c3 ("x86/xen: Make get_debugreg() noinstr")
7361fac0465b ("x86/xen: Make set_debugreg() noinstr")
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists