linux-kernel - Re: relax_domain_level boot parameter has no effect

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 04 Jun 2012 17:37:42 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Dimitri Sivanich <sivanich@....com>
Cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: relax_domain_level boot parameter has no effect

On Fri, 2012-06-01 at 16:03 -0500, Dimitri Sivanich wrote:
> I noticed (and verified) that the relax_domain_level boot parameter does not
> get processed because sched_domain_level_max is 0 at the time that
> setup_relax_domain_level() is run.
> 
> int sched_domain_level_max;
> 
> static int __init setup_relax_domain_level(char *str)
> {
>         unsigned long val;
> 
>         val = simple_strtoul(str, NULL, 0);
>         if (val < sched_domain_level_max)
>                 default_relax_domain_level = val;
> 
>         return 1;
> }
> __setup("relax_domain_level=", setup_relax_domain_level);

Ah indeed.. this has been so for a while I guess.

What are you using this knob for?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/