On Fri, 2018-06-22 at 10:01 -0700, Dave Hansen wrote: > On 06/20/2018 12:56 PM, Rik van Riel wrote: > > +#define TLBSTATE_OK 0 > > +#define TLBSTATE_LAZY 1 > > Could we spell out a bit more about what "OK" means in comments? It > obviously means "not lazy", but anything else?
After discussion with Andy, I plan to simply drop this patch, and use memory ordering between updating tlbstate.is_lazy and *.tlb_gen to take care of getting the TLB reloaded at context switch time if needed. We should not need the extra TLBSTATE_FLUSH state, so a boolean is fine and this patch is unnecessary. -- All Rights Reversed.
signature.asc
Description: This is a digitally signed message part
