| 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
| ||
|
Date: Thu, 28 Mar 2013 10:51:11 -0400 (EDT) From: Nicolas Pitre <nicolas.pitre@...aro.org> To: Stefano Stabellini <stefano.stabellini@...citrix.com> cc: Will Deacon <will.deacon@....com>, "xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, "arnd@...db.de" <arnd@...db.de>, Marc Zyngier <Marc.Zyngier@....com>, "linux@....linux.org.uk" <linux@....linux.org.uk> Subject: Re: [PATCH v3] [RFC] arm: use PSCI if available On Thu, 28 Mar 2013, Stefano Stabellini wrote: > - the interface to bring up secondary cpus is different and based on > PSCI, in fact Xen is going to add a PSCI node to the device tree so that > Dom0 can use it. > > Oh wait, Dom0 is not going to use the PSCI interface even if the node is > present on device tree because it's going to prefer the platform smp_ops > instead. Waitaminute... I must have missed this part. Who said platform specific methods must be used in preference to PSCI? If DT does provide PSCI description, then PSCI should be used. Doing otherwise is senseless. If PSCI is not to be used, then it should not be present in DT. Nicolas -- 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