| 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
| ||
|
Message-ID: <57de88af-b7a7-2214-95c3-26917e00a175@linux.intel.com>
Date: Fri, 22 Jun 2018 10:01:56 -0700
From: Dave Hansen <dave.hansen@...ux.intel.com>
To: Rik van Riel <riel@...riel.com>, linux-kernel@...r.kernel.org
Cc: 86@...r.kernel.org, luto@...nel.org, mingo@...nel.org,
tglx@...utronix.de, efault@....de, songliubraving@...com,
kernel-team@...com
Subject: Re: [PATCH 3/7] x86,tlb: change tlbstate.is_lazy to tlbstate.state
On 06/20/2018 12:56 PM, Rik van Riel wrote:
> +#define TLBSTATE_OK 0
> +#define TLBSTATE_LAZY 1
Could we spell out a bit more about what "OK" means in comments? It
obviously means "not lazy", but anything else?
Powered by blists - more mailing lists