From: Peter Zijlstra <peterz@infradead.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org, ndesaulniers@google.com
Subject: Re: [peterz-queue:sched/idle 45/48] vmlinux.o: warning: objtool: enter_s2idle_proper+0x78: call to ct_cpuidle_exit() leaves .noinstr.text section
Date: Thu, 22 Sep 2022 16:13:22 +0200 [thread overview]
Message-ID: <Yyxtgs/jRYcyH43f@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <202209220456.cXRrGXs7-lkp@intel.com>
On Thu, Sep 22, 2022 at 04:34:47AM +0800, kernel test robot wrote:
> >> vmlinux.o: warning: objtool: enter_s2idle_proper+0x78: call to ct_cpuidle_exit() leaves .noinstr.text section
> >> vmlinux.o: warning: objtool: cpuidle_enter_state+0x111: call to ct_cpuidle_exit() leaves .noinstr.text section
include/linux/cpuidle.h:static __always_inline void ct_cpuidle_exit(void)
Dear LLVM folks, ... WTF ?!?
prev parent reply other threads:[~2022-09-22 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 20:34 [peterz-queue:sched/idle 45/48] vmlinux.o: warning: objtool: enter_s2idle_proper+0x78: call to ct_cpuidle_exit() leaves .noinstr.text section kernel test robot
2022-09-22 14:13 ` 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=Yyxtgs/jRYcyH43f@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=ndesaulniers@google.com \
/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