From: Peter Zijlstra <peterz@infradead.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
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>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: linux-next: Tree for Jan 5 (objtool: 3 warnings)
Date: Wed, 6 Jan 2021 11:56:09 +0100 [thread overview]
Message-ID: <X/WXSVdqLsX3JE9Z@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20210105225228.vtg2zbpn4oud4qth@treble>
On Tue, Jan 05, 2021 at 04:52:28PM -0600, Josh Poimboeuf wrote:
> On Tue, Jan 05, 2021 at 12:48:20PM -0800, Randy Dunlap wrote:
> > On 1/4/21 6:50 PM, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Changes since 20210104:
> > >
> >
> > on x86_64:
> >
> > vmlinux.o: warning: objtool: __do_fast_syscall_32()+0x47: call to syscall_enter_from_user_mode_work() leaves .noinstr.text section
> > vmlinux.o: warning: objtool: __sev_es_nmi_complete()+0xc7: call to sev_es_wr_ghcb_msr() leaves .noinstr.text section
> > vmlinux.o: warning: objtool: lock_is_held_type()+0xb: call to lockdep_enabled() leaves .noinstr.text section
> >
> >
> > Full randconfig file is attached.
>
> These look like legit noinstr warnings. Thomas, Peter?
Aye, let me get on that.
prev parent reply other threads:[~2021-01-06 10:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 2:50 linux-next: Tree for Jan 5 Stephen Rothwell
2021-01-05 20:42 ` linux-next: Tree for Jan 5 (drivers/usb/cdns3/cdnsp-pci.o) Randy Dunlap
2021-01-05 20:48 ` linux-next: Tree for Jan 5 (objtool: 3 warnings) Randy Dunlap
2021-01-05 22:52 ` Josh Poimboeuf
2021-01-06 10:56 ` 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=X/WXSVdqLsX3JE9Z@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.