[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <198b5e75-f96e-0d3b-912b-ad3d24c2569d@redhat.com>
Date: Thu, 10 Sep 2020 15:57:14 +0200
From: David Hildenbrand <david@...hat.com>
To: Michal Hocko <mhocko@...e.com>
Cc: Oscar Salvador <osalvador@...e.de>,
Laurent Dufour <ldufour@...ux.ibm.com>,
akpm@...ux-foundation.org, rafael@...nel.org,
nathanl@...ux.ibm.com, cheloha@...ux.ibm.com,
stable@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-mm@...ck.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm: don't rely on system state to detect hot-plug
operations
>> Also, under QEMU, just do a reboot with hotplugged memory and you're in
>> the very same situation.
>
> OK, I didn't know that. I thought the memory would be presented as a
> normal memory after reboot. Thanks for the clarification.
That's one of the cases where QEMU differs to actual hardware - it's not
added to e820, so ACPI always probes+detects+adds DIMMs during boot.
Some people (me :)) consider that a feature and not a BUG.
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists