From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751651AbdGZMar (ORCPT ); Wed, 26 Jul 2017 08:30:47 -0400 Received: from mx2.suse.de ([195.135.220.15]:58498 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751538AbdGZMaq (ORCPT ); Wed, 26 Jul 2017 08:30:46 -0400 Date: Wed, 26 Jul 2017 14:30:41 +0200 From: Michal Hocko To: Heiko Carstens Cc: linux-mm@kvack.org, Andrew Morton , Mel Gorman , Vlastimil Babka , Andrea Arcangeli , Jerome Glisse , Reza Arbab , Yasuaki Ishimatsu , qiuxishi@huawei.com, Kani Toshimitsu , slaoub@gmail.com, Joonsoo Kim , Andi Kleen , Daniel Kiper , Igor Mammedov , Vitaly Kuznetsov , LKML , Benjamin Herrenschmidt , Dan Williams , "H. Peter Anvin" , Ingo Molnar , Michael Ellerman , Paul Mackerras , Thomas Gleixner , Gerald Schaefer Subject: Re: [RFC PATCH 3/5] mm, memory_hotplug: allocate memmap from the added memory range for sparse-vmemmap Message-ID: <20170726123040.GO2981@dhcp22.suse.cz> References: <20170726083333.17754-1-mhocko@kernel.org> <20170726083333.17754-4-mhocko@kernel.org> <20170726114539.GG3218@osiris> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170726114539.GG3218@osiris> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 26-07-17 13:45:39, Heiko Carstens wrote: [...] > In general I do like your idea, however if I understand your patches > correctly we might have an ordering problem on s390: it is not possible to > access hot-added memory on s390 before it is online (MEM_GOING_ONLINE > succeeded). Could you point me to the code please? I cannot seem to find the notifier which implements that. > On MEM_GOING_ONLINE we ask the hypervisor to back the potential available > hot-added memory region with physical pages. Accessing those ranges before > that will result in an exception. Can we make the range which backs the memmap range available? E.g from s390 specific __vmemmap_populate path? > However with your approach the memory is still allocated when add_memory() > is being called, correct? That wouldn't be a change to the current > behaviour; except for the ordering problem outlined above. Could you be more specific please? I do not change when the memmap is allocated. -- Michal Hocko SUSE Labs