Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932319AbcLHSmp (ORCPT ); Thu, 8 Dec 2016 13:42:45 -0500 Received: from mail-ua0-f169.google.com ([209.85.217.169]:34686 "EHLO mail-ua0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753220AbcLHSmm (ORCPT ); Thu, 8 Dec 2016 13:42:42 -0500 MIME-Version: 1.0 In-Reply-To: <20161208162150.148763-26-kirill.shutemov@linux.intel.com> References: <20161208162150.148763-1-kirill.shutemov@linux.intel.com> <20161208162150.148763-26-kirill.shutemov@linux.intel.com> From: Andy Lutomirski Date: Thu, 8 Dec 2016 10:42:19 -0800 Message-ID: Subject: Re: [RFC, PATCHv1 24/28] x86/mm: add sync_global_pgds() for configuration with 5-level paging To: "Kirill A. Shutemov" Cc: Linus Torvalds , Andrew Morton , X86 ML , Thomas Gleixner , Ingo Molnar , Arnd Bergmann , "H. Peter Anvin" , Andi Kleen , Dave Hansen , linux-arch , "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1755 Lines: 41 On Thu, Dec 8, 2016 at 8:21 AM, Kirill A. Shutemov wrote: > This basically restores slightly modified version of original > sync_global_pgds() which we had before foldedl p4d was introduced. > > The only modification is protection against 'address' overflow. > > Signed-off-by: Kirill A. Shutemov > --- > arch/x86/mm/init_64.c | 47 +++++++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 47 insertions(+) > > diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c > index a991f5c4c2c4..d637893ac8c2 100644 > --- a/arch/x86/mm/init_64.c > +++ b/arch/x86/mm/init_64.c > @@ -92,6 +92,52 @@ __setup("noexec32=", nonx32_setup); > * When memory was added/removed make sure all the processes MM have > * suitable PGD entries in the local PGD level page. > */ > +#ifdef CONFIG_X86_5LEVEL > +void sync_global_pgds(unsigned long start, unsigned long end, int removed) > +{ > + unsigned long address; > + > + for (address = start; address <= end && address >= start; > + address += PGDIR_SIZE) { > + const pgd_t *pgd_ref = pgd_offset_k(address); > + struct page *page; > + > + /* > + * When it is called after memory hot remove, pgd_none() > + * returns true. In this case (removed == 1), we must clear > + * the PGD entries in the local PGD level page. > + */ > + if (pgd_none(*pgd_ref) && !removed) > + continue; This isn't quite specific to your patch, but can we assert that, if removed=1, then we're not operating on the vmalloc range? Because if we do, this will be racy is nasty ways.