linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Jann Horn <jannh@google.com>
Cc: kernel test robot <rong.a.chen@intel.com>,
	Maddie Stone <maddiestone@google.com>,
	Kees Cook <keescook@chromium.org>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Will Deacon <will.deacon@arm.com>,
	lkp@lists.01.org
Subject: Re: [kernel] 247f5d7caa: will-it-scale.per_process_ops 9.6% improvement
Date: Fri, 21 Feb 2020 16:00:54 +0000	[thread overview]
Message-ID: <20200221160053.GA19330@willie-the-truck> (raw)
In-Reply-To: <CAG48ez0N9rTEtrA1TrL07r5Om_yK-10XO2XtsWOn3Nde0PXsZA@mail.gmail.com>

On Fri, Feb 21, 2020 at 04:55:42PM +0100, Jann Horn wrote:
> On Fri, Feb 21, 2020 at 12:56 PM kernel test robot
> <rong.a.chen@intel.com> wrote:
> > FYI, we noticed a 9.6% improvement of will-it-scale.per_process_ops due to commit:
> >
> >
> > commit: 247f5d7caa443d0ea5f1992aeda875e679e9bd35 ("kernel-hacking: Make DEBUG_{LIST,PLIST,SG,NOTIFIERS} non-debug options")
> > https://git.kernel.org/cgit/linux/kernel/git/will/linux.git debug-list
> 
> I'm guessing this might mean that the test bot had the DEBUG_LIST
> stuff enabled in its Kconfig, whereas after the rename, the default is
> used, which is off?

I thought that at first, but scrolling down in the logs of the report
I got totally confused by the softirqs and interrupts stuff.

> This seems a bit problematic if people had DEBUG_LIST enabled in their
> old kernel config and then try to reuse that config for a new kernel.
> I wonder whether it'd be acceptable to keep the options under their
> old names and let them "select" the new ones, or whether we have to
> choose between "keep the old bad name" and "discard people's old
> config flags".

I can keep DEBUG_LIST kicking around and have the options default to that.
Once I've finished updated lkdtm, I'll post this all out to the list.

Will

  reply	other threads:[~2020-02-21 16:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 11:55 [kernel] 247f5d7caa: will-it-scale.per_process_ops 9.6% improvement kernel test robot
2020-02-21 15:55 ` Jann Horn
2020-02-21 16:00   ` Will Deacon [this message]
2020-02-21 16:29 ` Jann Horn

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=20200221160053.GA19330@willie-the-truck \
    --to=will@kernel.org \
    --cc=jannh@google.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@lists.01.org \
    --cc=maddiestone@google.com \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rong.a.chen@intel.com \
    --cc=will.deacon@arm.com \
    /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;
as well as URLs for NNTP newsgroup(s).