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]
Message-ID: <20150213230137.GH8656@n2100.arm.linux.org.uk>
Date:	Fri, 13 Feb 2015 23:01:37 +0000
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Magnus Damm <magnus.damm@...il.com>
Cc:	Stephen Boyd <sboyd@...eaurora.org>,
	Simon Horman <horms@...ge.net.au>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Mark Rutland <mark.rutland@....com>,
	Nicolas Pitre <nico@...aro.org>,
	Dave Martin <Dave.Martin@....com>,
	SH-Linux <linux-sh@...r.kernel.org>
Subject: Re: [PATCH v2] ARM: smp: Only expose /sys/.../cpuX/online if
 hotpluggable

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.

However, cleaning things up by removing unnecessary cpu_disable
methods is a good thing to do irrespective of that.

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ