All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] ARM: smp: Only expose /sys/.../cpuX/online if hotpluggable
Date: Mon, 16 Feb 2015 15:29:48 +0000	[thread overview]
Message-ID: <20150216152948.GH8994@leverpostej> (raw)
In-Reply-To: <20150213230137.GH8656@n2100.arm.linux.org.uk>

On Fri, Feb 13, 2015 at 11:01:37PM +0000, Russell King - ARM Linux wrote:
> On Fri, Feb 13, 2015 at 09:44:50PM +0000, Magnus Damm wrote:
> > Also, based on the comment in mcpm_cpu_can_disable() it looks like the
> > PSCI hook may be executed once only with your change in place?
> > Hopefully PSCI is OK not being invoked for every CPU shutdown.
> 
> This is why I've said (in the parent thread) that I'm not happy to
> apply this patch.  Mark Rutland has indicated that he has MCPM cases
> where the CPUs which can be disabled changes dynamically according
> to the secure firmware requirements, and ripping out todays
> infrastructure in light of that, only to have to add it back again
> later makes no sense.

To clarify, PSCI and MCPM are unrelated. It was originally conceived
that MCPM would use PSCI as a backend, but it turns out that they're
effectively mutually exclusive, and are handled separately. I still want
to add support for MIGRATE in the PSCI client code, but this is
independent of MCPM.

In some cases it's possible to determine at boot time that a CPU cannot
be hotplugged (e.g. in PSCI if the TOS is non-migrateable), so having
separate hooks for determining that static and dynamic ability to
hotplug a CPU sounds reasonable to me.

Thanks,
Mark.

WARNING: multiple messages have this Message-ID (diff)
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: smp: Only expose /sys/.../cpuX/online if hotpluggable
Date: Mon, 16 Feb 2015 15:29:48 +0000	[thread overview]
Message-ID: <20150216152948.GH8994@leverpostej> (raw)
In-Reply-To: <20150213230137.GH8656@n2100.arm.linux.org.uk>

On Fri, Feb 13, 2015 at 11:01:37PM +0000, Russell King - ARM Linux wrote:
> On Fri, Feb 13, 2015 at 09:44:50PM +0000, Magnus Damm wrote:
> > Also, based on the comment in mcpm_cpu_can_disable() it looks like the
> > PSCI hook may be executed once only with your change in place?
> > Hopefully PSCI is OK not being invoked for every CPU shutdown.
> 
> This is why I've said (in the parent thread) that I'm not happy to
> apply this patch.  Mark Rutland has indicated that he has MCPM cases
> where the CPUs which can be disabled changes dynamically according
> to the secure firmware requirements, and ripping out todays
> infrastructure in light of that, only to have to add it back again
> later makes no sense.

To clarify, PSCI and MCPM are unrelated. It was originally conceived
that MCPM would use PSCI as a backend, but it turns out that they're
effectively mutually exclusive, and are handled separately. I still want
to add support for MIGRATE in the PSCI client code, but this is
independent of MCPM.

In some cases it's possible to determine at boot time that a CPU cannot
be hotplugged (e.g. in PSCI if the TOS is non-migrateable), so having
separate hooks for determining that static and dynamic ability to
hotplug a CPU sounds reasonable to me.

Thanks,
Mark.

WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland@arm.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Simon Horman <horms@verge.net.au>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Nicolas Pitre <nico@linaro.org>,
	Dave P Martin <Dave.Martin@arm.com>,
	SH-Linux <linux-sh@vger.kernel.org>
Subject: Re: [PATCH v2] ARM: smp: Only expose /sys/.../cpuX/online if hotpluggable
Date: Mon, 16 Feb 2015 15:29:48 +0000	[thread overview]
Message-ID: <20150216152948.GH8994@leverpostej> (raw)
In-Reply-To: <20150213230137.GH8656@n2100.arm.linux.org.uk>

On Fri, Feb 13, 2015 at 11:01:37PM +0000, Russell King - ARM Linux wrote:
> On Fri, Feb 13, 2015 at 09:44:50PM +0000, Magnus Damm wrote:
> > Also, based on the comment in mcpm_cpu_can_disable() it looks like the
> > PSCI hook may be executed once only with your change in place?
> > Hopefully PSCI is OK not being invoked for every CPU shutdown.
> 
> This is why I've said (in the parent thread) that I'm not happy to
> apply this patch.  Mark Rutland has indicated that he has MCPM cases
> where the CPUs which can be disabled changes dynamically according
> to the secure firmware requirements, and ripping out todays
> infrastructure in light of that, only to have to add it back again
> later makes no sense.

To clarify, PSCI and MCPM are unrelated. It was originally conceived
that MCPM would use PSCI as a backend, but it turns out that they're
effectively mutually exclusive, and are handled separately. I still want
to add support for MIGRATE in the PSCI client code, but this is
independent of MCPM.

In some cases it's possible to determine at boot time that a CPU cannot
be hotplugged (e.g. in PSCI if the TOS is non-migrateable), so having
separate hooks for determining that static and dynamic ability to
hotplug a CPU sounds reasonable to me.

Thanks,
Mark.

  parent reply	other threads:[~2015-02-16 15:29 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 18:06 [PATCH v2] ARM: smp: Only expose /sys/.../cpuX/online if hotpluggable Stephen Boyd
2015-02-13 18:06 ` Stephen Boyd
2015-02-13 18:06 ` Stephen Boyd
2015-02-13 20:20 ` Simon Horman
2015-02-13 20:20   ` Simon Horman
2015-02-13 20:20   ` Simon Horman
2015-02-13 20:23   ` Stephen Boyd
2015-02-13 20:23     ` Stephen Boyd
2015-02-13 20:23     ` Stephen Boyd
2015-02-13 20:54     ` Magnus Damm
2015-02-13 20:54       ` Magnus Damm
2015-02-13 20:54       ` Magnus Damm
2015-02-13 20:59       ` Stephen Boyd
2015-02-13 20:59         ` Stephen Boyd
2015-02-13 20:59         ` Stephen Boyd
2015-02-13 21:44         ` Magnus Damm
2015-02-13 21:44           ` Magnus Damm
2015-02-13 21:44           ` Magnus Damm
2015-02-13 23:01           ` Russell King - ARM Linux
2015-02-13 23:01             ` Russell King - ARM Linux
2015-02-13 23:01             ` Russell King - ARM Linux
2015-02-14  0:01             ` Stephen Boyd
2015-02-14  0:01               ` Stephen Boyd
2015-02-14  0:01               ` Stephen Boyd
2015-02-14 10:01             ` Magnus Damm
2015-02-14 10:01               ` Magnus Damm
2015-02-14 10:01               ` Magnus Damm
2015-02-16 15:29             ` Mark Rutland [this message]
2015-02-16 15:29               ` Mark Rutland
2015-02-16 15:29               ` Mark Rutland
2015-02-13 22:58       ` Russell King - ARM Linux
2015-02-13 22:58         ` Russell King - ARM Linux
2015-02-13 22:58         ` Russell King - ARM Linux
2015-02-13 22:57   ` Russell King - ARM Linux
2015-02-13 22:57     ` Russell King - ARM Linux
2015-02-13 22:57     ` Russell King - ARM Linux
2015-02-13 23:24     ` Simon Horman
2015-02-13 23:24       ` Simon Horman
2015-02-13 23:24       ` Simon Horman

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=20150216152948.GH8994@leverpostej \
    --to=mark.rutland@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.