On Thu, 28 Jun 2012 12:55:04 +0200 Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote: > On Wed, 2012-06-27 at 16:33 -0700, Linus Torvalds wrote: > > IOW, the point I'm trying to make is that even if there are zero > > *actual* accesses of user space (because user space is dead, and the > > kernel hopefully does no "get_user()/put_user()" stuff at this point > > any more), the CPU may speculatively use user addresses for the > > bog-standard kernel addresses that happen. > > Right.. and s390 having done this only says that s390 appears to be ok > with it. Martin, does s390 hardware guarantee no speculative stuff like > Linus explained, or might there even be a latent issue on s390? The cpu can create speculative TLB entries, but only if it runs in the mode that uses the respective mm. We have two mm's active at the same time, the kernel mm (init_mm) and the user mm. While the cpu runs only in kernel mode it is not allowed to create TLBs for the user mm. While running in user mode it is allowed to speculatively create TLBs. > But it looks like we cannot do this in general, and esp. ARM (as already > noted by Catalin) has very aggressive speculative behaviour. > > The alternative is that we do a switch_mm() to init_mm instead of the > TLB flush. On x86 that should be about the same cost, but I've not > looked at other architectures yet. > > The second and least favourite alternative is of course special casing > this for s390 if it turns out its a safe thing to do for them. > > /me goes look through arch code. Basically we have two special requirements on s390: 1) do not modify ptes while attached to another cpu except with the special IPTE / IDTE instructions 2) do a TLB flush before freeing any kind of page table page, s390 needs a flush for pud, pmd & pte tables. -- blue skies, Martin. "Reality continues to ruin my life." - Calvin. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>