On Fri, Aug 03, 2018 at 08:40:25AM -0700, Reinette Chatre wrote:
> > Can we just get rid of WBINVD?
>
> While directed at me I am not able to answer this. native_wbinvd() is
> used in a few areas that appear important to me.
Some, like the crusty AGP gart or boot time mem_encrypt usage is fine,
On Fri, Aug 03, 2018 at 08:40:25AM -0700, Reinette Chatre wrote:
> > Can we just get rid of WBINVD?
>
> While directed at me I am not able to answer this. native_wbinvd() is
> used in a few areas that appear important to me.
Some, like the crusty AGP gart or boot time mem_encrypt usage is fine,
Hi Thomas,
On 8/3/2018 4:45 AM, Thomas Gleixner wrote:
> On Tue, 24 Jul 2018, Reinette Chatre wrote:
>> A Cache Pseudo-Locked region is vulnerable to certain instructions (INVD,
>> WBINVD, CLFLUSH) or deeper C-states (that could shrink or power off the
>> cache) evicting the pseudo-locked memory.
Hi Thomas,
On 8/3/2018 4:45 AM, Thomas Gleixner wrote:
> On Tue, 24 Jul 2018, Reinette Chatre wrote:
>> A Cache Pseudo-Locked region is vulnerable to certain instructions (INVD,
>> WBINVD, CLFLUSH) or deeper C-states (that could shrink or power off the
>> cache) evicting the pseudo-locked memory.
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 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 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
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
On Tue, 24 Jul 2018, Reinette Chatre wrote:
> Dear Maintainers,
>
> A Cache Pseudo-Locked region is vulnerable to certain instructions (INVD,
> WBINVD, CLFLUSH) or deeper C-states (that could shrink or power off the
> cache) evicting the pseudo-locked memory. The current support for
>
On Tue, 24 Jul 2018, Reinette Chatre wrote:
> Dear Maintainers,
>
> A Cache Pseudo-Locked region is vulnerable to certain instructions (INVD,
> WBINVD, CLFLUSH) or deeper C-states (that could shrink or power off the
> cache) evicting the pseudo-locked memory. The current support for
>
Dear Maintainers,
A Cache Pseudo-Locked region is vulnerable to certain instructions (INVD,
WBINVD, CLFLUSH) or deeper C-states (that could shrink or power off the
cache) evicting the pseudo-locked memory. The current support for
pseudo-locked regions already restrict deeper C-states on cores
Dear Maintainers,
A Cache Pseudo-Locked region is vulnerable to certain instructions (INVD,
WBINVD, CLFLUSH) or deeper C-states (that could shrink or power off the
cache) evicting the pseudo-locked memory. The current support for
pseudo-locked regions already restrict deeper C-states on cores
12 matches
Mail list logo
