From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6744CC34026 for ; Tue, 18 Feb 2020 09:19:08 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 3099320722 for ; Tue, 18 Feb 2020 09:19:07 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3099320722 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=vega.pgw.jp Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 9D4DF6B0003; Tue, 18 Feb 2020 04:19:07 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 985706B0006; Tue, 18 Feb 2020 04:19:07 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 89A6E6B0007; Tue, 18 Feb 2020 04:19:07 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0164.hostedemail.com [216.40.44.164]) by kanga.kvack.org (Postfix) with ESMTP id 6ECB56B0003 for ; Tue, 18 Feb 2020 04:19:07 -0500 (EST) Received: from smtpin05.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay03.hostedemail.com (Postfix) with ESMTP id 043338248D7C for ; Tue, 18 Feb 2020 09:19:07 +0000 (UTC) X-FDA: 76502698734.05.knot35_4f6af8ba2b352 X-HE-Tag: knot35_4f6af8ba2b352 X-Filterd-Recvd-Size: 2001 Received: from auth.gate-on.net (auth.Gate-On.Net [210.197.74.24]) by imf39.hostedemail.com (Postfix) with ESMTP for ; Tue, 18 Feb 2020 09:19:05 +0000 (UTC) Received: from vega.pgw.jp (w0109-49-135-103-152.uqwimax.jp [49.135.103.152]) by auth.gate-on.net (Postfix) with ESMTP id 17B13C267E; Tue, 18 Feb 2020 18:19:02 +0900 (JST) Received: from localhost (vega.pgw.jp [10.5.0.30]) by vega.pgw.jp (Postfix) with SMTP id AED28A53D; Tue, 18 Feb 2020 18:19:00 +0900 (JST) From: To: mhocko@kernel.org Cc: bhe@redhat.com, david@redhat.com, osalvador@suse.de, bugzilla-daemon@bugzilla.kernel.org, akpm@linux-foundation.org, richardw.yang@linux.intel.com, n-horiguchi@ah.jp.nec.com, linux-mm@kvack.org, kkabe@vega.pgw.jp Subject: Re: [Bug 206401] kernel panic on Hyper-V after 5 minutes due to memory hot-add In-Reply-To: Your message of "Tue, 18 Feb 2020 09:47:00 +0100". <20200218084700.GD21113@dhcp22.suse.cz> X-Mailer: mnews [version 1.22PL5] 2002-11-27(Wed) Date: Tue, 18 Feb 2020 18:19:00 +0900 Message-ID: <200218181900.M0115079@vega.pgw.jp> X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: mhocko@kernel.org sed in <20200218084700.GD21113@dhcp22.suse.cz> >> On Tue 18-02-20 15:24:48, kkabe@vega.pgw.jp wrote: >> [...] >> > Tried out the above patch. >> > It seems to be working; no panic, total memory has increased and >> > the hot-added memory is added as HIGHMEM. >> >> I was about to post a patch to mark hotplug broken on 32b but it seems >> you do care about this setup. Could you describe your usecase please? My usecase is testing out the kernel on Hyper-V before loading it on real i686 machine. Hyper-V machine is faster to skim out other bugs. So memory hot-add is not a must requirement for me, but having hot-add may be handy to see the application memory requirement. (as in the anaconda test revealed) If we're disabling it, we have to announce it somewhere; where is appropriate? `modinfo hv_balloon`'s "hot_add" description? -- kabe