From: Steven Rostedt <rostedt@goodmis.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
mbenes@suse.cz, x86@kernel.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
Date: Wed, 6 Apr 2022 10:14:21 -0400 [thread overview]
Message-ID: <20220406101421.3f67cf46@gandalf.local.home> (raw)
In-Reply-To: <20220406053251.6dyfxrjmmgdwocfc@treble>
On Tue, 5 Apr 2022 22:32:51 -0700
Josh Poimboeuf <jpoimboe@redhat.com> wrote:
> > See the comment in the header file you are patching:
> >
> > * This is intended as a debugging tool for the developer only.
> > * Please refrain from leaving trace_printks scattered around in
> > * your code. (Extra memory is used for special buffers that are
> > * allocated when trace_printk() is used.)
>
> So what do we do ... send a nastygram?
We already do. When anything with a trace_printk() is loaded, the dmesg
will display:
**********************************************************
** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
** **
** trace_printk() being used. Allocating extra memory. **
** **
** This means that this is a DEBUG kernel and it is **
** unsafe for production use. **
** **
** If you see this message and you are not debugging **
** the kernel, report this immediately to your vendor! **
** **
** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
**********************************************************
:-)
-- Steve
prev parent reply other threads:[~2022-04-06 16:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 4:33 kernel test robot
2022-04-05 14:01 ` Peter Zijlstra
2022-04-06 0:05 ` Josh Poimboeuf
2022-04-06 0:46 ` Thomas Gleixner
2022-04-06 1:20 ` Steven Rostedt
2022-04-06 18:44 ` Arnaldo Carvalho de Melo
2022-04-06 5:32 ` Josh Poimboeuf
2022-04-06 7:29 ` Peter Zijlstra
2022-04-06 14:19 ` Steven Rostedt
2022-04-06 7:43 ` Peter Zijlstra
2022-04-06 16:37 ` Josh Poimboeuf
2022-04-07 9:24 ` Peter Zijlstra
2022-04-06 14:14 ` Steven Rostedt [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=20220406101421.3f67cf46@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=jpoimboe@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mbenes@suse.cz \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®