2018-01-10 19:56 GMT+01:00 Maxime Villard <[email protected]>: > That's what we do, too. Doing this is faster than "unmapping the kernel pages > on return to user space". > > Switching the address space costs one "movq %rax,%cr3".
Yes, but address space switch also causes an implicit TLB/paging structure cache flush when not using something like PCID, doesn't it? >> Do you reckon SVS has potential of having lower overall overhead than >> separate address spaces + PCID? Alternatively, do you think SVS would benefit >> if we added PCID support to x86 pmap? > > Yes, it would benefit if we added PCID. Okay, I'll look into this. The feature seems pretty simple to use, though it will need some care to allow inactive processes to relinguish PCID when there is shortage. I'll try to not disturb your SVS work. > Probably, but there are still many CPUs without PCID out there, and for them > a blunt separation will unfortunately still be needed. Haswell and later have it. Latest benchmarks for Linux and Windows confirm the performance impact of their sw mitigations is significantly higher on CPUs without PCID, so it's all the more important to have this too. Jaromir
