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: <9e5fed54-d1ee-4001-9835-e9aa7b4a3ce0@intel.com>
Date: Tue, 18 Jun 2024 08:46:59 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Borislav Petkov <bp@...nel.org>, "H. Peter Anvin" <hpa@...or.com>,
 Sean Christopherson <seanjc@...gle.com>
Cc: X86 ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
 "Borislav Petkov (AMD)" <bp@...en8.de>
Subject: Re: [RFC PATCH] x86/cpufeatures: Flip the /proc/cpuinfo appearance
 logic

On 6/18/24 04:38, Borislav Petkov wrote:
> Flip the logic to make it explicit: an explicit "<name>" in the comment
> adds the flag to /proc/cpuinfo and otherwise not, by default.

This makes a lot of sense.  Historically, it seems like most things were
exposed in /proc/cpuinfo, but that trend has reversed and it's becoming
the exception rather than the rule.

Acked-by: Dave Hansen <dave.hansen@...ux.intel.com>



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ