linux-kernel - Re: sched domains oddness.

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:	Fri, 31 Oct 2008 10:58:14 -0700
From:	Suresh Siddha <suresh.b.siddha@...el.com>
To:	Dave Jones <davej@...hat.com>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>
Cc:	venkatesh.pallipadi@...el.com
Subject: Re: sched domains oddness.

On Fri, Oct 31, 2008 at 10:37:37AM -0700, Dave Jones wrote:
> Even curiouser.. When I unplug AC and replug it, it happens again, but slightly
> differently..
> 
> CPU0 attaching NULL sched-domain.
> CPU1 attaching NULL sched-domain.
> CPU0 attaching sched-domain:
>  domain 0: span 0-1 level MC
>   groups: 0 1
>   domain 1: span 0-1 level CPU
>    groups: 0-1
>    domain 2: span 0-1 level NODE
>     groups: 0-1
> CPU1 attaching sched-domain:
>  domain 0: span 0-1 level MC
>   groups: 1 0
>   domain 1: span 0-1 level CPU
>    groups: 0-1
>    domain 2: span 0-1 level NODE
>     groups: 0-1
> CPU0 attaching NULL sched-domain.
> CPU1 attaching NULL sched-domain.
> CPU0 attaching sched-domain:
>  domain 0: span 0-1 level MC
>   groups: 0 1
>   domain 1: span 0-1 level NODE
>    groups: 0-1
> CPU1 attaching sched-domain:
>  domain 0: span 0-1 level MC
>   groups: 1 0
>   domain 1: span 0-1 level NODE
>    groups: 0-1
> 
> 
> Note how the CPU level doesn't show up in the 2nd case.

This is def coming from sched_mc_power_savings. Some battery script
or something is getting notified and setting this value. Can you do
a grep from / for sched_mc_power_savings ?

> This still doesn't explain the flip-flop I saw just from booting,
> as that was on AC the whole time.

Boot messages are def something not related to sched_mc_power_savings.

thanks,
suresh
--
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/