linux-kernel - Re: [PATCH] Revert "arm64: Increase the max granular size"

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <56EAF8BA.8060305@codeaurora.org>
Date:	Thu, 17 Mar 2016 13:34:34 -0500
From:	Timur Tabi <timur@...eaurora.org>
To:	Andrew Pinski <apinski@...iumnetworks.com>,
	Catalin Marinas <catalin.marinas@....com>
Cc:	linux-arm-kernel@...ts.infradead.org,
	Ganesh Mahendran <opensource.ganesh@...il.com>,
	Will Deacon <will.deacon@....com>,
	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	rrichter@...ium.com, tchalamarla@...ium.com, apinski@...ium.com,
	Shanker Donthineni <shankerd@...eaurora.org>
Subject: Re: [PATCH] Revert "arm64: Increase the max granular size"

Andrew Pinski wrote:
>>
>
> Note ThunderX's SOC have customers  where some are embedded users
> (uboot) and server users (UEFI).  The cores always have 128 byte
> cacheline size.  So please don't make this dependent on ACPI.  Note the
> defconfig works correctly on T88.

This thread is getting off-topic.  There's nothing about the cacheline 
size that is dependent on ACPI or DT.  Catalin was wondering why we have 
our own defconfig for our ARM64 SOC, and I replied that it's because 
ACPI is not enabled yet in the upstream defconfig.

-- 
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum, a Linux Foundation collaborative project.