On 05/10/2016 08:57 AM, Borislav Petkov wrote: > On Tue, May 10, 2016 at 02:43:58PM +0100, Matt Fleming wrote: >> Is it not possible to maintain some kind of kernel virtual address >> mapping so memremap*() and friends can figure out when to twiddle the >> mapping attributes and map with/without encryption? > > I guess we can move the sme_* specific stuff one indirection layer > below, i.e., in the *memremap() routines so that callers don't have to > care... That should keep the churn down... > We could do that, but we'll have to generate that list of addresses so that it can be checked against the range being mapped. Since this is part of early memmap support searching that list every time might not be too bad. I'll have to look into that and see what that looks like. Thanks, Tom -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
