From: <kkabe@vega.pgw.jp>
To: mhocko@kernel.org
Cc: bhe@redhat.com, bugzilla-daemon@bugzilla.kernel.org,
akpm@linux-foundation.org, richardw.yang@linux.intel.com,
david@redhat.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
Date: Mon, 17 Feb 2020 20:21:32 +0900 [thread overview]
Message-ID: <200217202132.M0113661@vega.pgw.jp> (raw)
In-Reply-To: Your message of "Mon, 17 Feb 2020 11:33:35 +0100". <20200217103335.GI31531@dhcp22.suse.cz>
mhocko@kernel.org sed in <20200217103335.GI31531@dhcp22.suse.cz>
>> On Fri 14-02-20 23:26:29, kkabe@vega.pgw.jp wrote:
>> [...]
>> > [root@localhost ~]# [ 302.391125] hv_balloon: Max. dynamic memory size: 1048576 MB
>>
>> Is this saying that the system might hotplug up to 1TB of memory on this
>> 32b system?
Probably. Hypervisor API uses 64-bit values, so
that's why I added add_memory() printk to see if it's overflowing 4GB.
I guessed drivers/hv/hv_balloon.c:hv_mem_hot_add() needs a check to
not hot-add over 4GB memory on non-PAE systems and so on,
but that's another story.
>> Btw. the hotplug support on highmem systems is quite likely to be broken
>> and/or full of corner cases. I seriously doubt this is something anybody
>> should be running in production without a _lot_ of work.
>>
>> Is there any real usecase to run HyperV hotplug on 32b system?
>> --
>> Michal Hocko
>> SUSE Labs
next prev parent reply other threads:[~2020-02-17 11:21 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-206401-27@https.bugzilla.kernel.org/>
[not found] ` <bug-206401-27-zYD8WfDKqD@https.bugzilla.kernel.org/>
2020-02-10 5:32 ` Andrew Morton
2020-02-10 5:40 ` Baoquan He
2020-02-10 5:56 ` Andrew Morton
2020-02-10 6:09 ` Baoquan He
2020-02-10 6:15 ` Baoquan He
2020-02-10 23:07 ` Wei Yang
2020-02-12 0:41 ` Andrew Morton
2020-02-12 7:31 ` Baoquan He
2020-02-12 8:21 ` David Hildenbrand
2020-02-13 4:22 ` [Bug 206401] kernel panic on Hyper-V after 5 minutes due tomemory hot-add kabe
2020-02-13 8:19 ` Baoquan He
2020-02-14 14:26 ` [Bug 206401] kernel panic on Hyper-V after 5 minutes duetomemory hot-add kkabe
2020-02-14 14:48 ` Baoquan He
2020-02-14 15:01 ` Baoquan He
2020-02-17 4:48 ` Baoquan He
2020-02-17 5:31 ` [Bug 206401] kernel panic on Hyper-V after 5 minutes duetomemoryhot-add kkabe
2020-02-17 8:00 ` David Hildenbrand
2020-02-17 10:33 ` [Bug 206401] kernel panic on Hyper-V after 5 minutes duetomemory hot-add Michal Hocko
2020-02-17 11:21 ` kkabe [this message]
2020-02-17 5:46 ` [Bug 206401] kernel panic on Hyper-V after 5 minutes due to memory hot-add kkabe
2020-02-17 7:44 ` Baoquan He
2020-02-17 9:34 ` Oscar Salvador
2020-02-17 10:13 ` Baoquan He
2020-02-17 10:17 ` Baoquan He
2020-02-17 10:24 ` David Hildenbrand
2020-02-17 10:33 ` Baoquan He
2020-02-17 10:38 ` David Hildenbrand
2020-02-17 11:20 ` Baoquan He
2020-02-17 12:47 ` Michal Hocko
2020-02-18 6:24 ` kkabe
2020-02-18 8:47 ` Michal Hocko
2020-02-18 9:19 ` kkabe
2020-02-18 9:26 ` David Hildenbrand
2020-02-18 10:05 ` [RFC PATCH] memory_hotplug: disable the functionality for 32b (was: Re: [Bug 206401] kernel panic on Hyper-V after 5 minutes due to) " Michal Hocko
2020-02-18 10:11 ` David Hildenbrand
2020-02-19 3:23 ` Baoquan He
2020-02-19 21:46 ` Andrew Morton
2020-02-19 23:07 ` [RFC PATCH] memory_hotplug: disable the functionality for 32b Robin Murphy
2020-02-19 3:39 ` [Bug 206401] kernel panic on Hyper-V after 5 minutes due to memory hot-add Baoquan He
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200217202132.M0113661@vega.pgw.jp \
--to=kkabe@vega.pgw.jp \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=richardw.yang@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox