On Wed, Jan 10, 2018 at 09:59:01AM +0100, Ingo Molnar wrote:
>
> * Willy Tarreau wrote:
>
> > On Wed, Jan 10, 2018 at 09:01:02AM +0100, Ingo Molnar wrote:
> > >
> > > * Willy Tarreau wrote:
> > >
> > > > [...] If we had "pit_enabled", something like this could be confusing
> > > > because
>
* Willy Tarreau wrote:
> On Wed, Jan 10, 2018 at 09:01:02AM +0100, Ingo Molnar wrote:
> >
> > * Willy Tarreau wrote:
> >
> > > [...] If we had "pit_enabled", something like this could be confusing
> > > because
> > > it's not obvious whether this pti_enabled *enforces* PTI or if its
> > >
On Wed, Jan 10, 2018 at 09:01:02AM +0100, Ingo Molnar wrote:
>
> * Willy Tarreau wrote:
>
> > [...] If we had "pit_enabled", something like this could be confusing
> > because
> > it's not obvious whether this pti_enabled *enforces* PTI or if its absence
> > disables it :
> >
> > cmpb $0
* Willy Tarreau wrote:
> [...] If we had "pit_enabled", something like this could be confusing because
> it's not obvious whether this pti_enabled *enforces* PTI or if its absence
> disables it :
>
> cmpb $0, PER_CPU_VAR(pti_enabled)
> jz .Lend\@
The natural sequence would be:
On Wed, Jan 10, 2018 at 08:19:51AM +0100, Ingo Molnar wrote:
>
> * Willy Tarreau wrote:
>
> > +#ifdef CONFIG_PAGE_TABLE_ISOLATION
> > + this_cpu_write(pti_disable,
> > + next_p->mm && next_p->mm->context.pti_disable);
> > +#endif
>
> Another pet peeve, please write:
>
> > +
* Willy Tarreau wrote:
> +#ifdef CONFIG_PAGE_TABLE_ISOLATION
> + this_cpu_write(pti_disable,
> +next_p->mm && next_p->mm->context.pti_disable);
> +#endif
Another pet peeve, please write:
> + this_cpu_write(pti_disable, next_p->mm &&
> next_p->mm->context.pti_disabl
This one is updated upon each context switch to reflect the
crrent mm's pti_disable field.
Signed-off-by: Willy Tarreau
Cc: Andy Lutomirski
Cc: Borislav Petkov
Cc: Brian Gerst
Cc: Dave Hansen
Cc: Ingo Molnar
Cc: Linus Torvalds
Cc: Peter Zijlstra
Cc: Thomas Gleixner
Cc: Josh Poimboeuf
Cc:
7 matches
Mail list logo
