linux-kernel - Re: [RFC PATCH 0/7] x86/intel_rdt: Restoration of Cache Pseudo-Locked regions

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: <20180803144826.GL2458@hirez.programming.kicks-ass.net>
Date:   Fri, 3 Aug 2018 16:48:26 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Dave Hansen <dave.hansen@...el.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Reinette Chatre <reinette.chatre@...el.com>,
        fenghua.yu@...el.com, Tony Luck <tony.luck@...el.com>,
        vikas.shivappa@...ux.intel.com, gavin.hindman@...el.com,
        jithu.joseph@...el.com, mingo@...hat.com,
        "H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 0/7] x86/intel_rdt: Restoration of Cache
 Pseudo-Locked regions

On Fri, Aug 03, 2018 at 07:23:27AM -0700, Dave Hansen wrote:
> On 08/03/2018 04:45 AM, Thomas Gleixner wrote:
> >> Within the kernel two locations with direct invocations of the WBINVD
> >> instruction are coverted to native_wbinvd() and compile tested. Neither
> >> location is likely to be used on the platforms supporting Cache Pseudo-Locking.
> > Can we just get rid of WBINVD?
> 
> In general, or just this specific case?

In general I think. There aren't that many users IIRC.