All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: mingo@elte.hu, akpm@linux-foundation.org
Cc: maxk@qualcomm.com, schwidefsky@de.ibm.com, linux-kernel@vger.kernel.org
Subject: [PATCH/RESEND 0/2] sched: re-add removed arch_update_cpu_topology call
Date: Mon, 15 Dec 2008 15:34:37 +0100	[thread overview]
Message-ID: <20081215143437.843064041@de.ibm.com> (raw)

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.

             reply	other threads:[~2008-12-15 14:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-15 14:34 Heiko Carstens [this message]
2008-12-15 14:34 ` [PATCH/RESEND 1/2] sched: let arch_update_cpu_topology indicate if topology changed Heiko Carstens
2008-12-15 14:34 ` [PATCH/RESEND 2/2] sched: re-add missing arch_update_cpu_topology call Heiko Carstens

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=20081215143437.843064041@de.ibm.com \
    --to=heiko.carstens@de.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxk@qualcomm.com \
    --cc=mingo@elte.hu \
    --cc=schwidefsky@de.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.