linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Nicholas Piggin <npiggin@gmail.com>,
	Zhen Lei <thunder.leizhen@huawei.com>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
	Petr Mladek <pmladek@suse.com>
Cc: "Erhard F ." <erhard_f@mailbox.org>,
	kernel test robot <oliver.sang@intel.com>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	Zhen Lei <thunder.leizhen@huawei.com>
Subject: Re: [PATCH] kallsyms: Fix scheduling with interrupts disabled in self-test
Date: Thu, 12 Jan 2023 10:24:43 -0800	[thread overview]
Message-ID: <Y8BQaw5tVzDjZ9Sz@bombadil.infradead.org> (raw)
In-Reply-To: <20230112105426.1037325-1-npiggin@gmail.com>

On Thu, Jan 12, 2023 at 08:54:26PM +1000, Nicholas Piggin wrote:
> kallsyms_on_each* may schedule so must not be called with interrupts
> disabled. The iteration function could disable interrupts, but this
> also changes lookup_symbol() to match the change to the other timing
> code.
> 
> Reported-by: Erhard F. <erhard_f@mailbox.org>
> Link: https://lore.kernel.org/all/bug-216902-206035@https.bugzilla.kernel.org%2F/
> Reported-by: kernel test robot <oliver.sang@intel.com>
> Link: https://lore.kernel.org/oe-lkp/202212251728.8d0872ff-oliver.sang@intel.com
> Fixes: 30f3bb09778d ("kallsyms: Add self-test facility")
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> ---

Thanks Nicholas!

Petr had just suggested removing this aspect of the selftests, the performance
test as its specific to the config, it doesn't run many times to get an
average and odd things on a system can create different metrics. Zhen Lei
had given up on fixing it and has a patch to instead remove this part of
the selftest.

I still find value in keeping it, but Petr, would like your opinion on
this fix, if we were to keep it.

  Luis

>  kernel/kallsyms_selftest.c | 21 ++++++---------------
>  1 file changed, 6 insertions(+), 15 deletions(-)
> 
> diff --git a/kernel/kallsyms_selftest.c b/kernel/kallsyms_selftest.c
> index f35d9cc1aab1..bfbc12da3326 100644
> --- a/kernel/kallsyms_selftest.c
> +++ b/kernel/kallsyms_selftest.c
> @@ -157,14 +157,11 @@ static void test_kallsyms_compression_ratio(void)
>  static int lookup_name(void *data, const char *name, struct module *mod, unsigned long addr)
>  {
>  	u64 t0, t1, t;
> -	unsigned long flags;
>  	struct test_stat *stat = (struct test_stat *)data;
>  
> -	local_irq_save(flags);
> -	t0 = sched_clock();
> +	t0 = ktime_get_ns();
>  	(void)kallsyms_lookup_name(name);
> -	t1 = sched_clock();
> -	local_irq_restore(flags);
> +	t1 = ktime_get_ns();
>  
>  	t = t1 - t0;
>  	if (t < stat->min)
> @@ -234,18 +231,15 @@ static int find_symbol(void *data, const char *name, struct module *mod, unsigne
>  static void test_perf_kallsyms_on_each_symbol(void)
>  {
>  	u64 t0, t1;
> -	unsigned long flags;
>  	struct test_stat stat;
>  
>  	memset(&stat, 0, sizeof(stat));
>  	stat.max = INT_MAX;
>  	stat.name = stub_name;
>  	stat.perf = 1;
> -	local_irq_save(flags);
> -	t0 = sched_clock();
> +	t0 = ktime_get_ns();
>  	kallsyms_on_each_symbol(find_symbol, &stat);
> -	t1 = sched_clock();
> -	local_irq_restore(flags);
> +	t1 = ktime_get_ns();
>  	pr_info("kallsyms_on_each_symbol() traverse all: %lld ns\n", t1 - t0);
>  }
>  
> @@ -270,17 +264,14 @@ static int match_symbol(void *data, unsigned long addr)
>  static void test_perf_kallsyms_on_each_match_symbol(void)
>  {
>  	u64 t0, t1;
> -	unsigned long flags;
>  	struct test_stat stat;
>  
>  	memset(&stat, 0, sizeof(stat));
>  	stat.max = INT_MAX;
>  	stat.name = stub_name;
> -	local_irq_save(flags);
> -	t0 = sched_clock();
> +	t0 = ktime_get_ns();
>  	kallsyms_on_each_match_symbol(match_symbol, stat.name, &stat);
> -	t1 = sched_clock();
> -	local_irq_restore(flags);
> +	t1 = ktime_get_ns();
>  	pr_info("kallsyms_on_each_match_symbol() traverse all: %lld ns\n", t1 - t0);
>  }
>  
> -- 
> 2.37.2
> 

  parent reply	other threads:[~2023-01-12 18:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 10:54 [PATCH] kallsyms: Fix scheduling with interrupts disabled in self-test Nicholas Piggin
2023-01-12 17:30 ` Erhard F.
2023-01-12 18:24 ` Luis Chamberlain [this message]
2023-01-13  8:44   ` Petr Mladek
2023-01-13 23:13     ` Luis Chamberlain

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=Y8BQaw5tVzDjZ9Sz@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=erhard_f@mailbox.org \
    --cc=jikos@kernel.org \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mbenes@suse.cz \
    --cc=npiggin@gmail.com \
    --cc=oliver.sang@intel.com \
    --cc=pmladek@suse.com \
    --cc=thunder.leizhen@huawei.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).