[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <58128cae-5871-64d8-0b4a-c1e3bb354e95@rasmusvillemoes.dk>
Date: Tue, 26 Mar 2019 09:42:13 +0100
From: Rasmus Villemoes <linux@...musvillemoes.dk>
To: Andi Kleen <andi@...stfloor.org>, x86@...nel.org
Cc: akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
Andi Kleen <ak@...ux.intel.com>, herbert@...dor.apana.org.au
Subject: Re: [PATCH 14/17] crypto: Don't mark AES tables const and
cacheline_aligned
On 21/03/2019 23.00, Andi Kleen wrote:
> From: Andi Kleen <ak@...ux.intel.com>
>
> cacheline_aligned is a special section. It cannot be const at the same
> time because it's not read-only. It doesn't give any MMU protection.
Urgh. Perhaps this instead just wanted to use the quadruple underscore
version, ____cacheline_aligned ? That would make these objects correctly
aligned and still live in .rodata, no?
Rasmus
Powered by blists - more mailing lists