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: <20160111100644.GD9554@e104818-lin.cambridge.arm.com>
Date:	Mon, 11 Jan 2016 10:06:44 +0000
From:	Catalin Marinas <catalin.marinas@....com>
To:	Lorenzo Pieralisi <lorenzo.pieralisi@....com>
Cc:	Zhaoyang Huang <zhaoyang.huang@...aro.org>,
	zhaoyang.huang@...eadtrum.com, will.deacon@....com,
	linux-kernel@...r.kernel.org, hanjun.guo@...aro.org,
	suzuki.poulose@....com, Mark Rutland <mark.rutland@....com>
Subject: Re: [RFC PATCH] Add IPI entry for CPU UP

On Mon, Jan 11, 2016 at 09:59:25AM +0000, Lorenzo Pieralisi wrote:
> On Mon, Jan 11, 2016 at 03:10:40PM +0800, Zhaoyang Huang wrote:
> > In some ARM SOCs, IPI interrupt is used for hotplug in one cpu, that is,
> > sending a IPI to the core in WFI and powerdown status. So Add a IPI
> > entry for handle this kind of cpu up interrupt
> 
> On arm64 SOCs, with a mainline kernel, you can only hotplug CPUs out
> and back in by using the PSCI firmware interface, which does not
> require an IPI to boot a CPU, therefore this patch is useless.

I fully agree.

BTW, such patches should cc linux-arm-kernel@...ts.infradead.org as well
since they are ARM related.

-- 
Catalin

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ