On 12/17/2016 07:14 PM, David Miller wrote: > From: Mike Kravetz <mike.kravetz@xxxxxxxxxx> > Date: Fri, 16 Dec 2016 10:35:27 -0800 > >> In current code, only context ID register 0 is set and used by the MMU. >> On sun4v platforms that support MMU shared context, there is an additional >> context ID register: specifically context register 1. When searching >> the TLB, the MMU will find a match if the virtual address matches and >> the ID contained in context register 0 -OR- context register 1 matches. >> >> Load the shared context ID into context ID register 1. Care must be >> taken to load register 1 after register 0, as loading register 0 >> overwrites both register 0 and 1. Modify code loading register 0 to >> also load register one if applicable. >> >> Signed-off-by: Mike Kravetz <mike.kravetz@xxxxxxxxxx> > > You can't make these register accesses if the feature isn't being > used. > > Considering the percentage of applications which will actually use > this thing, incuring the overhead of even loading the shared context > register is simply unacceptable. Ok, let me try to find a way to eliminate these loads unless the application is using shared context. Part of the issue is a 'backwards compatibility' feature of the processor which loads/overwrites register 1 every time register 0 is loaded. Somewhere in the evolution of the processor, a feature was added so that register 0 could be loaded without overwriting register 1. That could be used to eliminate the extra load in some/many cases. But, that would likely lead to more runtime kernel patching based on processor level. And, I don't really want to add more of that if possible. Or, perhaps we only enable the shared context ID feature on processors which have the ability to work around the backwards compatibility feature. -- Mike Kravetz -- 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>