linux-kernel - Re: [RFC][PATCH 09/34] x86/cpu: Introduce address configuration structure

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: <b18d2563-0ce8-41d5-bc48-bce9042da6db@intel.com>
Date: Wed, 28 Feb 2024 09:29:05 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: "Huang, Kai" <kai.huang@...el.com>,
 Dave Hansen <dave.hansen@...ux.intel.com>, linux-kernel@...r.kernel.org
Cc: kirill.shutemov@...ux.intel.com, pbonzini@...hat.com, tglx@...utronix.de,
 x86@...nel.org, bp@...en8.de
Subject: Re: [RFC][PATCH 09/34] x86/cpu: Introduce address configuration
 structure

On 2/27/24 15:47, Huang, Kai wrote:
> From the above description, ...
> 
>> +struct x86_addr_config bsp_addr_config;
>> +
> 
> ... this can be __ro_after_init?
> 
> Maybe I am missing something, but if it cannot be annotated with
> __ro_after_init here, IMHO it would be helpful to call out in the
> changelog.

It can actually be full on __init .. eventually.  It goes *AWAY* after boot.

I'll add a note in the changelog why it can't be until later in the series.