Re: Spectre V1 diagnostic / mitigation

2018-12-19 Thread Richard Biener
On Wed, 19 Dec 2018, Richard Earnshaw (lists) wrote: > On 19/12/2018 17:17, Richard Biener wrote: > > On Wed, 19 Dec 2018, Florian Weimer wrote: > > > >> * Peter Bergner: > >> > >>> On 12/19/18 7:59 AM, Florian Weimer wrote: > * Richard Biener: > > > Sure, if we'd ever deploy this i

Re: Spectre V1 diagnostic / mitigation

2018-12-19 Thread Richard Earnshaw (lists)
On 19/12/2018 17:17, Richard Biener wrote: > On Wed, 19 Dec 2018, Florian Weimer wrote: > >> * Peter Bergner: >> >>> On 12/19/18 7:59 AM, Florian Weimer wrote: * Richard Biener: > Sure, if we'd ever deploy this in production placing this in the > TCB for glibc targets might be be

Re: Spectre V1 diagnostic / mitigation

2018-12-19 Thread Richard Biener
On Wed, 19 Dec 2018, Richard Earnshaw (lists) wrote: > On 19/12/2018 11:25, Richard Biener wrote: > > On Tue, 18 Dec 2018, Richard Earnshaw (lists) wrote: > > > >> On 18/12/2018 15:36, Richard Biener wrote: > >>> > >>> Hi, > >>> > >>> in the past weeks I've been looking into prototyping both spec

Re: Spectre V1 diagnostic / mitigation

2018-12-19 Thread Richard Biener
On Wed, 19 Dec 2018, Florian Weimer wrote: > * Peter Bergner: > > > On 12/19/18 7:59 AM, Florian Weimer wrote: > >> * Richard Biener: > >> > >>> Sure, if we'd ever deploy this in production placing this in the > >>> TCB for glibc targets might be beneifical. But as said the > >>> current implem

Re: Spectre V1 diagnostic / mitigation

2018-12-19 Thread Florian Weimer
* Peter Bergner: > On 12/19/18 7:59 AM, Florian Weimer wrote: >> * Richard Biener: >> >>> Sure, if we'd ever deploy this in production placing this in the >>> TCB for glibc targets might be beneifical. But as said the >>> current implementation was just an experiment intended to be >>> maximum p

Re: Spectre V1 diagnostic / mitigation

2018-12-19 Thread Richard Earnshaw (lists)
On 19/12/2018 11:25, Richard Biener wrote: > On Tue, 18 Dec 2018, Richard Earnshaw (lists) wrote: > >> On 18/12/2018 15:36, Richard Biener wrote: >>> >>> Hi, >>> >>> in the past weeks I've been looking into prototyping both spectre V1 >>> (speculative array bound bypass) diagnostics and mitigatio

Re: Spectre V1 diagnostic / mitigation

2018-12-19 Thread Peter Bergner
On 12/19/18 7:59 AM, Florian Weimer wrote: > * Richard Biener: > >> Sure, if we'd ever deploy this in production placing this in the >> TCB for glibc targets might be beneifical. But as said the >> current implementation was just an experiment intended to be >> maximum portable. I suppose the dy

Re: Spectre V1 diagnostic / mitigation

2018-12-19 Thread Florian Weimer
* Richard Biener: > Sure, if we'd ever deploy this in production placing this in the > TCB for glibc targets might be beneifical. But as said the > current implementation was just an experiment intended to be > maximum portable. I suppose the dynamic loader takes care > of initializing the TCB d

Re: Spectre V1 diagnostic / mitigation

2018-12-19 Thread Richard Biener
On Wed, 19 Dec 2018, Florian Weimer wrote: > * Richard Biener: > > > On Wed, 19 Dec 2018, Florian Weimer wrote: > > > >> * Richard Biener: > >> > >> > The cost is probably target dependent - on x86 it's simply a $fs based > >> > load/store. > >> > >> Do you need to reserve something in the TCB

Re: Spectre V1 diagnostic / mitigation

2018-12-19 Thread Florian Weimer
* Richard Biener: > On Wed, 19 Dec 2018, Florian Weimer wrote: > >> * Richard Biener: >> >> > The cost is probably target dependent - on x86 it's simply a $fs based >> > load/store. >> >> Do you need to reserve something in the TCB for this? > > No idea. But I figured using TLS with the patch o

Re: Spectre V1 diagnostic / mitigation

2018-12-19 Thread Richard Biener
On Wed, 19 Dec 2018, Florian Weimer wrote: > * Richard Biener: > > > The cost is probably target dependent - on x86 it's simply a $fs based > > load/store. > > Do you need to reserve something in the TCB for this? No idea. But I figured using TLS with the patch only works when optimizing and n

Re: Spectre V1 diagnostic / mitigation

2018-12-19 Thread Florian Weimer
* Richard Biener: > The cost is probably target dependent - on x86 it's simply a $fs based > load/store. Do you need to reserve something in the TCB for this? Thanks, Florian

Re: Spectre V1 diagnostic / mitigation

2018-12-19 Thread Richard Biener
On Tue, 18 Dec 2018, Richard Earnshaw (lists) wrote: > On 18/12/2018 15:36, Richard Biener wrote: > > > > Hi, > > > > in the past weeks I've been looking into prototyping both spectre V1 > > (speculative array bound bypass) diagnostics and mitigation in an > > architecture independent manner to

Re: Spectre V1 diagnostic / mitigation

2018-12-19 Thread Richard Biener
On Tue, 18 Dec 2018, Jeff Law wrote: > On 12/18/18 8:36 AM, Richard Biener wrote: > > > > Hi, > > > > in the past weeks I've been looking into prototyping both spectre V1 > > (speculative array bound bypass) diagnostics and mitigation in an > > architecture independent manner to assess feasabil

Re: Spectre V1 diagnostic / mitigation

2018-12-18 Thread Richard Earnshaw (lists)
On 18/12/2018 15:36, Richard Biener wrote: > > Hi, > > in the past weeks I've been looking into prototyping both spectre V1 > (speculative array bound bypass) diagnostics and mitigation in an > architecture independent manner to assess feasability and some kind > of upper bound on the performanc

Re: Spectre V1 diagnostic / mitigation

2018-12-18 Thread Jeff Law
On 12/18/18 8:36 AM, Richard Biener wrote: > > Hi, > > in the past weeks I've been looking into prototyping both spectre V1 > (speculative array bound bypass) diagnostics and mitigation in an > architecture independent manner to assess feasability and some kind > of upper bound on the performanc

Spectre V1 diagnostic / mitigation

2018-12-18 Thread Richard Biener
Hi, in the past weeks I've been looking into prototyping both spectre V1 (speculative array bound bypass) diagnostics and mitigation in an architecture independent manner to assess feasability and some kind of upper bound on the performance impact one can expect. https://lists.llvm.org/pipermai