Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753107AbcLHTd3 (ORCPT ); Thu, 8 Dec 2016 14:33:29 -0500 Received: from mail-wm0-f65.google.com ([74.125.82.65]:32971 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752863AbcLHTd2 (ORCPT ); Thu, 8 Dec 2016 14:33:28 -0500 Date: Thu, 8 Dec 2016 22:33:24 +0300 From: "Kirill A. Shutemov" To: Andy Lutomirski Cc: "Kirill A. Shutemov" , 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" Subject: Re: [RFC, PATCHv1 24/28] x86/mm: add sync_global_pgds() for configuration with 5-level paging Message-ID: <20161208193324.GD30380@node.shutemov.name> References: <20161208162150.148763-1-kirill.shutemov@linux.intel.com> <20161208162150.148763-26-kirill.shutemov@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2119 Lines: 51 On Thu, Dec 08, 2016 at 10:42:19AM -0800, Andy Lutomirski wrote: > 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. Looks like there's no users of removed=1. The last user is gone with af2cf278ef4f ("x86/mm/hotplug: Don't remove PGD entries in remove_pagetable()") I'll just drop it (with separate patch). -- Kirill A. Shutemov