On 04/24/2017 06:09 PM, David Miller wrote: > From: John Paul Adrian Glaubitz <glaubitz@xxxxxxxxxxxxxxxxxxx> > Date: Mon, 24 Apr 2017 22:37:40 +0200 > >> Would be really nice to able to have a canonical solution for this issue, >> it's been biting us on SPARC for quite a while now due to the fact that >> virtual address space has been 52 bits on SPARC for a while now. > > It's going to break again with things like ADI which encode protection > keys in the high bits of the 64-bit virtual address. > > Reallly, it would be nice if these tags were instead encoded in the > low bits of suitably aligned memory allocations but I am sure it's to > late to do that now. I'm curious (and hey, ARM has 52-bit VAs coming[0] that was added in ARMv8.2). Does anyone really think pointer tagging is a good idea for a new architecture being created going forward? This could be archived somewhere so that the folks in Berkeley and elsewhere have an answer. As an aside, one of the reasons I've been tracking these Intel patches personally is to figure out the best way to play out the ARMv8 story. There isn't the same legacy of precompiled code out there (and the things that broke and were fixed when moving from 42-bit to 48-bit VA are already accounting for a later switch to 52-bit). I do find it amusing that I proposed a solution similar Kirill's a year or so back to some other folks elsewhere with a similar set of goals in mind. Jon. [0] Requires 64K pages on ARMv8. It's one of the previously unmentioned reasons why RHEL for ARM was built with 64K granule size ;) -- 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>
