From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@kernel.org>
Subject: Re: vmlinux.o: warning: objtool: xen_sched_clock+0x4a: call to ftrace_likely_update() leaves .noinstr.text section
Date: Wed, 24 May 2023 14:01:02 -0700 [thread overview]
Message-ID: <20230524210102.h2bbhlvujcg77wuw@treble> (raw)
In-Reply-To: <20230524142954.GN4253@hirez.programming.kicks-ass.net>
On Wed, May 24, 2023 at 04:29:54PM +0200, Peter Zijlstra wrote:
> > vmlinux.o: warning: objtool: acpi_idle_enter+0x65: call to ftrace_likely_update() leaves .noinstr.text section
> > vmlinux.o: warning: objtool: ibt_selftest+0x1e: return with modified stack frame
>
> Robot folks; could you please discard all:
>
> ftrace_likey_update.*noinstr
>
> warnings, they're -EWONTFIX.
Could we just make CONFIG_TRACE_BRANCH_PROFILING incompatible with
CONFIG_NOINSTR_VALIDATION?
--
Josh
prev parent reply other threads:[~2023-05-24 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 14:22 vmlinux.o: warning: objtool: xen_sched_clock+0x4a: call to ftrace_likely_update() leaves .noinstr.text section kernel test robot
2023-05-24 14:29 ` Peter Zijlstra
2023-05-24 21:01 ` Josh Poimboeuf [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=20230524210102.h2bbhlvujcg77wuw@treble \
--to=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.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 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.