public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: linux-next: Tree for Aug 27 (objtool)
Date: Sat, 31 Aug 2019 00:14:27 +0900	[thread overview]
Message-ID: <20190831001427.4781757c2028e142bafc5446@kernel.org> (raw)
In-Reply-To: <20190830152351.9311610b5cffb93110cbd6da@kernel.org>

On Fri, 30 Aug 2019 15:23:51 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:

> > Actually I wonder if X86_DECODER_SELFTEST is even still needed these
> > days, since objtool is enabled on default configs.  Objtool already uses
> > the decoder to disassemble every instruction in the kernel (except for a
> > few whitelisted files).
> 
> Sometimes it have found bugs, so I would like to keep it. That test runs
> build time and in-kernel decoder is somewhat critical. It is better to
> run a test before install it.

But yes, I think it may not need to run always anymore. So let's make it
disabled by default.

Thank you,

-- 
Masami Hiramatsu <mhiramat@kernel.org>

      reply	other threads:[~2019-08-30 15:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27  9:05 linux-next: Tree for Aug 27 Stephen Rothwell
2019-08-27 15:18 ` linux-next: Tree for Aug 27 (amdgpu) Randy Dunlap
2019-08-27 15:41   ` Alex Deucher
2019-08-27 15:24 ` linux-next: Tree for Aug 27 (mshyperv.c) Randy Dunlap
2019-08-27 15:29 ` linux-next: Tree for Aug 27 (kunit) Randy Dunlap
2019-08-27 16:09   ` Brendan Higgins
2019-08-27 16:12     ` shuah
2019-08-27 15:37 ` linux-next: Tree for Aug 27 (mm/zsmalloc.c) Randy Dunlap
2019-08-28  5:30   ` Sergey Senozhatsky
2019-08-27 15:40 ` linux-next: Tree for Aug 27 (objtool) Randy Dunlap
2019-08-27 15:59   ` Josh Poimboeuf
2019-08-27 19:05     ` Randy Dunlap
2019-08-28 15:51       ` Josh Poimboeuf
2019-08-28 16:05         ` Randy Dunlap
2019-08-28 16:13           ` Josh Poimboeuf
2019-08-28 16:34             ` Josh Poimboeuf
2019-08-29  1:53               ` Masami Hiramatsu
2019-08-29 17:59                 ` Josh Poimboeuf
2019-08-30  6:23                   ` Masami Hiramatsu
2019-08-30 15:14                     ` Masami Hiramatsu [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=20190831001427.4781757c2028e142bafc5446@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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