|
|
Log in / Subscribe / Register

objtool/x86: noinstr vs PARAVIRT

From:  Peter Zijlstra <peterz-AT-infradead.org>
To:  jpoimboe-AT-redhat.com, tglx-AT-linutronix.de
Subject:  [PATCH v2 00/24] objtool/x86: noinstr vs PARAVIRT
Date:  Thu, 24 Jun 2021 11:40:59 +0200
Message-ID:  <20210624094059.886075998@infradead.org>
Cc:  linux-kernel-AT-vger.kernel.org, peterz-AT-infradead.org, joro-AT-8bytes.org, boris.ostrovsky-AT-oracle.com, jgross-AT-suse.com, x86-AT-kernel.org, mbenes-AT-suse.com, rostedt-AT-goodmis.org, dvyukov-AT-google.com, elver-AT-google.com
Archive-link:  Article

Hi,

Per long standing request from Thomas, this makes the noinstr validation work
with PARAVIRT=y.

It isn't exactly pretty, but it does work.

With all this on top of tip/master (which includes some of the previous round),
all (*) the robots seem to get is endless garbage like:

  vmlinux.o: warning: objtool: __rdgsbase_inactive()+0x24: call to ftrace_likely_update() leaves .noinstr.text section

And my secret plan is to pull the KPTI CR3 swizzling into C such that all that
will insta explode and become unfixable.

Steve, can I please delete TRACE_BRANCH_PROFILING and PROFILE_ALL_BRANCHES already?


(*) there were also a few reports from 0day running out of memory.



Copyright © 2021, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds