From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752621AbdJTJm3 (ORCPT ); Fri, 20 Oct 2017 05:42:29 -0400 Received: from mga05.intel.com ([192.55.52.43]:10383 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751866AbdJTJm1 (ORCPT ); Fri, 20 Oct 2017 05:42:27 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.43,405,1503385200"; d="scan'208";a="325550613" Date: Fri, 20 Oct 2017 12:41:52 +0300 From: "Kirill A. Shutemov" To: Ingo Molnar Cc: "Kirill A. Shutemov" , Ingo Molnar , Linus Torvalds , x86@kernel.org, Thomas Gleixner , "H. Peter Anvin" , Andrew Morton , Andy Lutomirski , Cyrill Gorcunov , Borislav Petkov , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/6] Boot-time switching between 4- and 5-level paging for 4.15, Part 1 Message-ID: <20171020094152.skx5sh5ramq2a3vu@black.fi.intel.com> References: <20170929140821.37654-1-kirill.shutemov@linux.intel.com> <20171003082754.no6ym45oirah53zp@node.shutemov.name> <20171017154241.f4zaxakfl7fcrdz5@node.shutemov.name> <20171020081853.lmnvaiydxhy5c63t@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171020081853.lmnvaiydxhy5c63t@gmail.com> User-Agent: NeoMutt/20170714-126-deb55f (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 20, 2017 at 08:18:53AM +0000, Ingo Molnar wrote: > > * Kirill A. Shutemov wrote: > > > On Tue, Oct 03, 2017 at 11:27:54AM +0300, Kirill A. Shutemov wrote: > > > On Fri, Sep 29, 2017 at 05:08:15PM +0300, Kirill A. Shutemov wrote: > > > > The first bunch of patches that prepare kernel to boot-time switching > > > > between paging modes. > > > > > > > > Please review and consider applying. > > > > > > Ping? > > > > Ingo, is there anything I can do to get review easier for you? > > Yeah, what is the conclusion on the sub-discussion of patch #2: > > [PATCH 2/6] mm/zsmalloc: Prepare to variable MAX_PHYSMEM_BITS > > ... do we want to skip it entirely and use the other 5 patches? Yes, please. MAX_PHYSMEM_BITS not variable yet in this part of the series. And I will post some version the patch in the next part, if it will be required. -- Kirill A. Shutemov