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: Wed, 24 Feb 2016 10:07:44 -0800 From: David Daney <ddaney@...iumnetworks.com> To: Will Deacon <will.deacon@....com> CC: Marc Zyngier <marc.zyngier@....com>, Catalin Marinas <catalin.marinas@....com>, David Daney <ddaney.cavm@...il.com>, <linux-arm-kernel@...ts.infradead.org>, Mark Rutland <mark.rutland@....com>, <linux-kernel@...r.kernel.org>, Andrew Pinski <apinski@...ium.com>, David Daney <david.daney@...ium.com> Subject: Re: [PATCH v3] arm64: Add workaround for Cavium erratum 27456 On 02/24/2016 10:06 AM, Will Deacon wrote: > On Wed, Feb 24, 2016 at 10:03:02AM -0800, David Daney wrote: >> On 02/24/2016 06:07 AM, Marc Zyngier wrote: >>> On 24/02/16 13:40, Will Deacon wrote: >>> >>> [...] >>> >>>> (and Catalin, if you pick this up, watch out for the conflicts in >>>> cpufeature.h) >>> >>> Yup, that one is about to become a minefield (ARM64_HAS_NO_HW_PREFETCH, >>> ARM64_HAS_UAO, ARM64_ALT_PAN_NOT_UAO and ARM64_HAS_VIRT_HOST_EXTN are >>> already happily clashing into -next). But hey, the more the merrier! ;-) >>> >> >> Would you like me to rebase it to for-next/core ? > > I think ARM64_HAS_VIRT_HOST_EXTN is in the KVM tree, so you're probably > best off looking at linux-next and choosing your feature number based on > that, whilst basing the patch on either for-next/core or mainline. > OK, I will do that now. David. > Will >
Powered by blists - more mailing lists