linux-kernel - [PATCH/RESEND 0/2] sched: re-add removed arch_update_cpu

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-next>] [day] [month] [year] [list]

Message-Id: <20081215143437.843064041@de.ibm.com>
Date:	Mon, 15 Dec 2008 15:34:37 +0100
From:	Heiko Carstens <heiko.carstens@...ibm.com>
To:	mingo@...e.hu, akpm@...ux-foundation.org
Cc:	maxk@...lcomm.com, schwidefsky@...ibm.com,
	linux-kernel@...r.kernel.org
Subject: [PATCH/RESEND 0/2] sched: re-add removed arch_update_cpu_topology call

This fixes a regression introduced with
e761b7725234276a802322549cee5255305a0930 ("cpu hotplug, sched:
Introduce cpu_active_map and redo sched domain managment (take 2)":

arch_reinit_sched_domains used to call arch_update_cpu_topology
via arch_init_sched_domains. This call got lost with the above
mentioned patch.

So we might end up with outdated and missing cpus in the cpu core
maps (s390 used to call arch_reinit_sched_domains if cpu topology changed).

This patch set changes arch_update_cpu_topology so that it can indicate
if the cpu topology changed and adds a call to arch_update_cpu_topology
in partition_sched_domains which gets called whenever scheduling domains
get updated.
So whenever architecture code detects that cpu topology changed it might
force an update of the scheduling domains by calling arch_reinit_sched_domains
or rebuild_sched_domains.

Besides that the first patch also adds a comment to arch_update_cpu_topology
so that its purpose gets described, since most people seem to expect that
cpu core mappings are stable which isn't necessarily the case.
--
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/