Re: proposal for meltdown-workaround with low overhead

Hi Tony, at least in the original Paper ( meltdownattack.com/meltdown.pdf ) and in Wikipedia ( en.wikipedia.org/wiki/Meltdown_(security_vulnerability) ) indicate, that the exception variant is the preferred choice (even if it is also possible via branch prediction bending). (I assume, that

Re: proposal for meltdown-workaround with low overhead

Hi Tony, at least in the original Paper ( meltdownattack.com/meltdown.pdf ) and in Wikipedia ( en.wikipedia.org/wiki/Meltdown_(security_vulnerability) ) indicate, that the exception variant is the preferred choice (even if it is also possible via branch prediction bending). (I assume, that

Re: proposal for meltdown-workaround with low overhead

On Thu, 4 Jan 2018 15:09:28 -0800 Tony Luck wrote: > On Thu, Jan 4, 2018 at 11:45 AM, Alexander Kleinsorge > wrote: > > As Meltdown-Issue depends on allowing to cause many exceptions (usually : > > accessing an invalid address), we could restrict

Re: proposal for meltdown-workaround with low overhead

On Thu, 4 Jan 2018 15:09:28 -0800 Tony Luck wrote: > On Thu, Jan 4, 2018 at 11:45 AM, Alexander Kleinsorge > wrote: > > As Meltdown-Issue depends on allowing to cause many exceptions (usually : > > accessing an invalid address), we could restrict this misusage easy. > > The accesses to the

Re: proposal for meltdown-workaround with low overhead

On Thu, Jan 4, 2018 at 11:45 AM, Alexander Kleinsorge wrote: > As Meltdown-Issue depends on allowing to cause many exceptions (usually : > accessing an invalid address), we could restrict this misusage easy. The accesses to the invalid address are performed

Re: proposal for meltdown-workaround with low overhead

On Thu, Jan 4, 2018 at 11:45 AM, Alexander Kleinsorge wrote: > As Meltdown-Issue depends on allowing to cause many exceptions (usually : > accessing an invalid address), we could restrict this misusage easy. The accesses to the invalid address are performed speculatively by the CPU in a code

proposal for meltdown-workaround with low overhead

Hi all, This is my first post here and I hope it is fine. I will subscribe tomorrow to this list, so please take me in CC for answers now. As Meltdown-Issue depends on allowing to cause many exceptions (usually : accessing an invalid address), we could restrict this misusage easy. My rough

proposal for meltdown-workaround with low overhead

Hi all, This is my first post here and I hope it is fine. I will subscribe tomorrow to this list, so please take me in CC for answers now. As Meltdown-Issue depends on allowing to cause many exceptions (usually : accessing an invalid address), we could restrict this misusage easy. My rough