From: Michal =?UTF-8?B?U3VjaMOhbmVr?= Subject: Re: [PATCH RFC] mm/memory_hotplug: Introduce memory block types Date: Thu, 4 Oct 2018 17:28:07 +0200 Message-ID: <20181004172807.1eef3a6b@kitsune.suse.cz> References: <20181001084038.GD18290@dhcp22.suse.cz> <20181002134734.GT18290@dhcp22.suse.cz> <98fb8d65-b641-2225-f842-8804c6f79a06@redhat.com> <8736tndubn.fsf@vitty.brq.redhat.com> <20181003134444.GH4714@dhcp22.suse.cz> <87zhvvcf3b.fsf@vitty.brq.redhat.com> <49456818-238e-2d95-9df6-d1934e9c8b53@linux.intel.com> <87tvm3cd5w.fsf@vitty.brq.redhat.com> <06a35970-e478-18f8-eae6-4022925a5192@redhat.com> <20181004061938.GB22173@dhcp22.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: driverdev-devel-bounces@linuxdriverproject.org Sender: "devel" To: David Hildenbrand Cc: Kate Stewart , Rich Felker , linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org, Peter Zijlstra , Dave Hansen , Heiko Carstens , Michal Hocko , linux-mm@kvack.org, Paul Mackerras , "H. Peter Anvin" , Rashmica Gupta , Boris Ostrovsky , Stephen Rothwell , Michael Neuling , Stephen Hemminger , Yoshinori Sato , Vitaly Kuznetsov , linux-acpi@vger.kernel.org, Ingo Molnar , xen-devel@lists.xenproject.org, Rob Herring , Len Brown , Pavel Tatashin , linux-s390@v List-Id: linux-acpi@vger.kernel.org On Thu, 4 Oct 2018 10:13:48 +0200 David Hildenbrand wrote: ok, so what is the problem here? Handling the hotplug in userspace through udev may be suboptimal and kernel handling might be faster but that's orthogonal to the problem at hand. The state of the art is to determine what to do with hotplugged memory in userspace based on platform and virtualization type. Changing the default to depend on the driver that added the memory rather than platform type should solve the issue of VMs growing different types of memory device emulation. Am I missing something? Thanks Michal