Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp1412235pxk; Thu, 10 Sep 2020 14:53:16 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxbl0SCPSaVIPcJLzmVx7F5XR20FTMlnWpHHqN6vMsshMmtwB8nK1jzF3p1B7DDGOIgXCMD X-Received: by 2002:a50:cf8a:: with SMTP id h10mr11851130edk.43.1599774795941; Thu, 10 Sep 2020 14:53:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1599774795; cv=none; d=google.com; s=arc-20160816; b=VKUd6CDOOEyR8sK73DPsCpV8dvp8qSYR2zFI/HxOmuMq/MKGX5SdKA8fCk9UjDPOOp PvD+R5sCALYbnFE9+7D3o56WLPzQEPKZuqVj+6PS3u6dIUSVRkBbSngUk8Kxvtwud8hY Yo/CVu0+K4R/CFLb8zud9PpB+uziJNL9xvkpytalPT/IfAO0VIyWDRKsDFWe4jzqacmq w+A2PkLiOYeAlhJtXYEsEF6fCCV5OymOQWld3qLcRcwv2fxmMS/MEQFsHGJzmWXZX4Qk zdv5cFiMS0Ptf3mmxqD1hCKitSsbXbSK7K71ecJeqFl8FvqqRJujktjk9RZqRh2OpaLP yiVA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:organization:autocrypt:from:references:cc:to:subject :dkim-signature; bh=rTcgO8BSFM6RFn95+Uz0g2g2Wy581v0xHwoGs0qnLrI=; b=bXxDU2ZK8fC0kegAB+9LCeTZkwsZM7GOYlEtFjN/makJio74KrBNeTCFnIYPRHqwG+ DuH3RUl5ON6qYLgTvw+OZOKBa/YTIUOHRwsjNt/8AAzSgo8++AfpyjqMXQFLGuQACtJR Go7+15R7QBF9jP2OaC3tC8c+/ki8+KaPghy1ylby8NF5FZihf27xMX1Qox43+SlESPUZ mPxq462ol9NOT8o1lOjQPqjxTuo10deFfG5gDzopsEBDBwS1MpIR2D/0Fs3UkNiWlBVI 9Lz6IBlvLEXGNxmLG8gTBgbxWlb1jnXe9iuzdPXrcwlgKJMwUHmdGawQIat1vQ60/6kT 2Nfg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="M/9za64q"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c8si4397025ejx.605.2020.09.10.14.52.52; Thu, 10 Sep 2020 14:53:15 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="M/9za64q"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725875AbgIJVvX (ORCPT + 99 others); Thu, 10 Sep 2020 17:51:23 -0400 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:34722 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730794AbgIJMtt (ORCPT ); Thu, 10 Sep 2020 08:49:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1599742175; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:autocrypt:autocrypt; bh=rTcgO8BSFM6RFn95+Uz0g2g2Wy581v0xHwoGs0qnLrI=; b=M/9za64qpy7JC491OGCsQ6N3mRrSYfz1yZr79+a1AbSLNG1LVYYstKdWehli/14bjD1FlS y6MfMVOJn2saLMTBr8OrjidpY50mHDSnIgH6ERXvMoLeNgWwsfidigK0K2TQSXAjql56Bw CIuD7TK+c4Kj2NIueCn8zDPqTFgvCBk= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-206-Yoql_GzKOlSSRvWQJKHr_w-1; Thu, 10 Sep 2020 08:49:33 -0400 X-MC-Unique: Yoql_GzKOlSSRvWQJKHr_w-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id F090E10BBECB; Thu, 10 Sep 2020 12:49:31 +0000 (UTC) Received: from [10.36.113.88] (ovpn-113-88.ams2.redhat.com [10.36.113.88]) by smtp.corp.redhat.com (Postfix) with ESMTP id B3A8571775; Thu, 10 Sep 2020 12:49:29 +0000 (UTC) Subject: Re: [PATCH] mm: don't rely on system state to detect hot-plug operations To: Michal Hocko , Oscar Salvador Cc: Laurent Dufour , akpm@linux-foundation.org, rafael@kernel.org, nathanl@linux.ibm.com, cheloha@linux.ibm.com, stable@vger.kernel.org, Greg Kroah-Hartman , linux-mm@kvack.org, LKML References: <9faac1ce-c02d-7dbc-f79a-4aaaa5a73d28@linux.ibm.com> <20200909090953.GE7348@dhcp22.suse.cz> <4cdb54be-1a92-4ba4-6fee-3b415f3468a9@linux.ibm.com> <20200909105914.GF7348@dhcp22.suse.cz> <74a62b00-235e-7deb-2814-f3b240fea25e@linux.ibm.com> <20200910072331.GB28354@dhcp22.suse.cz> <31cfdf35-618f-6f56-ef16-0d999682ad02@linux.ibm.com> <20200910111246.GE28354@dhcp22.suse.cz> <20200910120343.GA6635@linux> <20200910124755.GG28354@dhcp22.suse.cz> From: David Hildenbrand Autocrypt: addr=david@redhat.com; prefer-encrypt=mutual; keydata= mQINBFXLn5EBEAC+zYvAFJxCBY9Tr1xZgcESmxVNI/0ffzE/ZQOiHJl6mGkmA1R7/uUpiCjJ dBrn+lhhOYjjNefFQou6478faXE6o2AhmebqT4KiQoUQFV4R7y1KMEKoSyy8hQaK1umALTdL QZLQMzNE74ap+GDK0wnacPQFpcG1AE9RMq3aeErY5tujekBS32jfC/7AnH7I0v1v1TbbK3Gp XNeiN4QroO+5qaSr0ID2sz5jtBLRb15RMre27E1ImpaIv2Jw8NJgW0k/D1RyKCwaTsgRdwuK Kx/Y91XuSBdz0uOyU/S8kM1+ag0wvsGlpBVxRR/xw/E8M7TEwuCZQArqqTCmkG6HGcXFT0V9 PXFNNgV5jXMQRwU0O/ztJIQqsE5LsUomE//bLwzj9IVsaQpKDqW6TAPjcdBDPLHvriq7kGjt WhVhdl0qEYB8lkBEU7V2Yb+SYhmhpDrti9Fq1EsmhiHSkxJcGREoMK/63r9WLZYI3+4W2rAc UucZa4OT27U5ZISjNg3Ev0rxU5UH2/pT4wJCfxwocmqaRr6UYmrtZmND89X0KigoFD/XSeVv jwBRNjPAubK9/k5NoRrYqztM9W6sJqrH8+UWZ1Idd/DdmogJh0gNC0+N42Za9yBRURfIdKSb B3JfpUqcWwE7vUaYrHG1nw54pLUoPG6sAA7Mehl3nd4pZUALHwARAQABtCREYXZpZCBIaWxk ZW5icmFuZCA8ZGF2aWRAcmVkaGF0LmNvbT6JAlgEEwEIAEICGwMGCwkIBwMCBhUIAgkKCwQW AgMBAh4BAheAAhkBFiEEG9nKrXNcTDpGDfzKTd4Q9wD/g1oFAl8Ox4kFCRKpKXgACgkQTd4Q 9wD/g1oHcA//a6Tj7SBNjFNM1iNhWUo1lxAja0lpSodSnB2g4FCZ4R61SBR4l/psBL73xktp rDHrx4aSpwkRP6Epu6mLvhlfjmkRG4OynJ5HG1gfv7RJJfnUdUM1z5kdS8JBrOhMJS2c/gPf wv1TGRq2XdMPnfY2o0CxRqpcLkx4vBODvJGl2mQyJF/gPepdDfcT8/PY9BJ7FL6Hrq1gnAo4 3Iv9qV0JiT2wmZciNyYQhmA1V6dyTRiQ4YAc31zOo2IM+xisPzeSHgw3ONY/XhYvfZ9r7W1l pNQdc2G+o4Di9NPFHQQhDw3YTRR1opJaTlRDzxYxzU6ZnUUBghxt9cwUWTpfCktkMZiPSDGd KgQBjnweV2jw9UOTxjb4LXqDjmSNkjDdQUOU69jGMUXgihvo4zhYcMX8F5gWdRtMR7DzW/YE BgVcyxNkMIXoY1aYj6npHYiNQesQlqjU6azjbH70/SXKM5tNRplgW8TNprMDuntdvV9wNkFs 9TyM02V5aWxFfI42+aivc4KEw69SE9KXwC7FSf5wXzuTot97N9Phj/Z3+jx443jo2NR34XgF 89cct7wJMjOF7bBefo0fPPZQuIma0Zym71cP61OP/i11ahNye6HGKfxGCOcs5wW9kRQEk8P9 M/k2wt3mt/fCQnuP/mWutNPt95w9wSsUyATLmtNrwccz63W5Ag0EVcufkQEQAOfX3n0g0fZz Bgm/S2zF/kxQKCEKP8ID+Vz8sy2GpDvveBq4H2Y34XWsT1zLJdvqPI4af4ZSMxuerWjXbVWb T6d4odQIG0fKx4F8NccDqbgHeZRNajXeeJ3R7gAzvWvQNLz4piHrO/B4tf8svmRBL0ZB5P5A 2uhdwLU3NZuK22zpNn4is87BPWF8HhY0L5fafgDMOqnf4guJVJPYNPhUFzXUbPqOKOkL8ojk CXxkOFHAbjstSK5Ca3fKquY3rdX3DNo+EL7FvAiw1mUtS+5GeYE+RMnDCsVFm/C7kY8c2d0G NWkB9pJM5+mnIoFNxy7YBcldYATVeOHoY4LyaUWNnAvFYWp08dHWfZo9WCiJMuTfgtH9tc75 7QanMVdPt6fDK8UUXIBLQ2TWr/sQKE9xtFuEmoQGlE1l6bGaDnnMLcYu+Asp3kDT0w4zYGsx 5r6XQVRH4+5N6eHZiaeYtFOujp5n+pjBaQK7wUUjDilPQ5QMzIuCL4YjVoylWiBNknvQWBXS lQCWmavOT9sttGQXdPCC5ynI+1ymZC1ORZKANLnRAb0NH/UCzcsstw2TAkFnMEbo9Zu9w7Kv AxBQXWeXhJI9XQssfrf4Gusdqx8nPEpfOqCtbbwJMATbHyqLt7/oz/5deGuwxgb65pWIzufa N7eop7uh+6bezi+rugUI+w6DABEBAAGJAjwEGAEIACYCGwwWIQQb2cqtc1xMOkYN/MpN3hD3 AP+DWgUCXw7HsgUJEqkpoQAKCRBN3hD3AP+DWrrpD/4qS3dyVRxDcDHIlmguXjC1Q5tZTwNB boaBTPHSy/Nksu0eY7x6HfQJ3xajVH32Ms6t1trDQmPx2iP5+7iDsb7OKAb5eOS8h+BEBDeq 3ecsQDv0fFJOA9ag5O3LLNk+3x3q7e0uo06XMaY7UHS341ozXUUI7wC7iKfoUTv03iO9El5f XpNMx/YrIMduZ2+nd9Di7o5+KIwlb2mAB9sTNHdMrXesX8eBL6T9b+MZJk+mZuPxKNVfEQMQ a5SxUEADIPQTPNvBewdeI80yeOCrN+Zzwy/Mrx9EPeu59Y5vSJOx/z6OUImD/GhX7Xvkt3kq Er5KTrJz3++B6SH9pum9PuoE/k+nntJkNMmQpR4MCBaV/J9gIOPGodDKnjdng+mXliF3Ptu6 3oxc2RCyGzTlxyMwuc2U5Q7KtUNTdDe8T0uE+9b8BLMVQDDfJjqY0VVqSUwImzTDLX9S4g/8 kC4HRcclk8hpyhY2jKGluZO0awwTIMgVEzmTyBphDg/Gx7dZU1Xf8HFuE+UZ5UDHDTnwgv7E th6RC9+WrhDNspZ9fJjKWRbveQgUFCpe1sa77LAw+XFrKmBHXp9ZVIe90RMe2tRL06BGiRZr jPrnvUsUUsjRoRNJjKKA/REq+sAnhkNPPZ/NNMjaZ5b8Tovi8C0tmxiCHaQYqj7G2rgnT0kt WNyWQQ== Organization: Red Hat GmbH Message-ID: <27e73d7d-c172-aa84-dad2-f97ed6123db4@redhat.com> Date: Thu, 10 Sep 2020 14:49:28 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: <20200910124755.GG28354@dhcp22.suse.cz> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10.09.20 14:47, Michal Hocko wrote: > On Thu 10-09-20 14:03:48, Oscar Salvador wrote: >> On Thu, Sep 10, 2020 at 01:35:32PM +0200, Laurent Dufour wrote: >> >>> That points has been raised by David, quoting him here: >>> >>>> IIRC, ACPI can hotadd memory while SCHEDULING, this patch would break that. >>>> >>>> Ccing Oscar, I think he mentioned recently that this is the case with ACPI. >>> >>> Oscar told that he need to investigate further on that. >> >> I think my reply got lost. >> >> We can see acpi hotplugs during SYSTEM_SCHEDULING: >> >> $QEMU -enable-kvm -machine pc -smp 4,sockets=4,cores=1,threads=1 -cpu host -monitor pty \ >> -m size=$MEM,slots=255,maxmem=4294967296k \ >> -numa node,nodeid=0,cpus=0-3,mem=512 -numa node,nodeid=1,mem=512 \ >> -object memory-backend-ram,id=memdimm0,size=134217728 -device pc-dimm,node=0,memdev=memdimm0,id=dimm0,slot=0 \ >> -object memory-backend-ram,id=memdimm1,size=134217728 -device pc-dimm,node=0,memdev=memdimm1,id=dimm1,slot=1 \ >> -object memory-backend-ram,id=memdimm2,size=134217728 -device pc-dimm,node=0,memdev=memdimm2,id=dimm2,slot=2 \ >> -object memory-backend-ram,id=memdimm3,size=134217728 -device pc-dimm,node=0,memdev=memdimm3,id=dimm3,slot=3 \ >> -object memory-backend-ram,id=memdimm4,size=134217728 -device pc-dimm,node=1,memdev=memdimm4,id=dimm4,slot=4 \ >> -object memory-backend-ram,id=memdimm5,size=134217728 -device pc-dimm,node=1,memdev=memdimm5,id=dimm5,slot=5 \ >> -object memory-backend-ram,id=memdimm6,size=134217728 -device pc-dimm,node=1,memdev=memdimm6,id=dimm6,slot=6 \ >> >> kernel: [ 0.753643] __add_memory: nid: 0 start: 0100000000 - 0108000000 (size: 134217728) >> kernel: [ 0.756950] register_mem_sect_under_node: system_state= 1 >> >> kernel: [ 0.760811] register_mem_sect_under_node+0x4f/0x230 >> kernel: [ 0.760811] walk_memory_blocks+0x80/0xc0 >> kernel: [ 0.760811] link_mem_sections+0x32/0x40 >> kernel: [ 0.760811] add_memory_resource+0x148/0x250 >> kernel: [ 0.760811] __add_memory+0x5b/0x90 >> kernel: [ 0.760811] acpi_memory_device_add+0x130/0x300 >> kernel: [ 0.760811] acpi_bus_attach+0x13c/0x1c0 >> kernel: [ 0.760811] acpi_bus_attach+0x60/0x1c0 >> kernel: [ 0.760811] acpi_bus_scan+0x33/0x70 >> kernel: [ 0.760811] acpi_scan_init+0xea/0x21b >> kernel: [ 0.760811] acpi_init+0x2f1/0x33c >> kernel: [ 0.760811] do_one_initcall+0x46/0x1f4 > > Is there any actual usecase for a configuration like this? What is the > point to statically define additional memory like this when the same can > be achieved on the same command line? You can online it movable right away to unplug later. Also, under QEMU, just do a reboot with hotplugged memory and you're in the very same situation. -- Thanks, David / dhildenb