> On May 14, 2019, at 10:15 AM, Andy Lutomirski wrote:
>
>
>
> On May 14, 2019, at 10:00 AM, Nadav Amit wrote:
>
>>> On May 14, 2019, at 1:00 AM, Paul Turner wrote:
>>>
>>> From: Nadav Amit
>>> Date: Fri, May 10, 2019 at 7:45 PM
>>> To:
>>> Cc: Borislav Petkov, , Nadav Amit, Andy
>>> Luto
On May 14, 2019, at 10:00 AM, Nadav Amit wrote:
>> On May 14, 2019, at 1:00 AM, Paul Turner wrote:
>>
>> From: Nadav Amit
>> Date: Fri, May 10, 2019 at 7:45 PM
>> To:
>> Cc: Borislav Petkov, , Nadav Amit, Andy
>> Lutomirsky, Ingo Molnar, Peter Zijlstra, Thomas Gleixner, Jann Horn
>>
>>> I
> On May 14, 2019, at 1:00 AM, Paul Turner wrote:
>
> From: Nadav Amit
> Date: Fri, May 10, 2019 at 7:45 PM
> To:
> Cc: Borislav Petkov, , Nadav Amit, Andy
> Lutomirsky, Ingo Molnar, Peter Zijlstra, Thomas Gleixner, Jann Horn
>
>> It may be useful to check in runtime whether certain assertions
From: Nadav Amit
Date: Fri, May 10, 2019 at 7:45 PM
To:
Cc: Borislav Petkov, , Nadav Amit, Andy
Lutomirsky, Ingo Molnar, Peter Zijlstra, Thomas Gleixner, Jann Horn
> It may be useful to check in runtime whether certain assertions are
> violated even during speculative execution. This can allow t
On 5/10/19 12:25 PM, Nadav Amit wrote:
> It may be useful to check in runtime whether certain assertions are
> violated even during speculative execution. This can allow to avoid
> adding unnecessary memory fences and at the same time check that no data
> leak channels exist.
>
> For example, addi
It may be useful to check in runtime whether certain assertions are
violated even during speculative execution. This can allow to avoid
adding unnecessary memory fences and at the same time check that no data
leak channels exist.
For example, adding such checks can show that allocating zeroed page
6 matches
Mail list logo
