[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220406074330.GD34954@worktop.programming.kicks-ass.net>
Date: Wed, 6 Apr 2022 09:43:30 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Josh Poimboeuf <jpoimboe@...hat.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
kernel test robot <lkp@...el.com>, kbuild-all@...ts.01.org,
linux-kernel@...r.kernel.org, mbenes@...e.cz, x86@...nel.org,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: drivers/gpu/drm/i915/i915.prelink.o: warning: objtool:
__intel_wait_for_register_fw.cold()+0xce: relocation to !ENDBR:
vlv_allow_gt_wake.cold+0x0
On Tue, Apr 05, 2022 at 10:32:51PM -0700, Josh Poimboeuf wrote:
> More broadly, this issue could theoretically happen in some other places
> throughout the kernel tree, since _THIS_IP_ is fundamentally unreliable
> as currently written.
>
> So we could look at making _THIS_IP_ more predictable.
>
> Inline asm would work better ("lea 0(%rip), %[rip]"), but then you need
> an arch-dependent implementation...
Well, there's a ton of _THIS_IP_ instances all around, and it would be
unfortunate to have them grow into actual code :/
Powered by blists - more mailing lists