From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:56005 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1729108AbgEARVb (ORCPT ); Fri, 1 May 2020 13:21:31 -0400 Subject: Re: [PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP References: <20200430102908.10107-1-david@redhat.com> <20200430102908.10107-3-david@redhat.com> <87pnbp2dcz.fsf@x220.int.ebiederm.org> <1b49c3be-6e2f-57cb-96f7-f66a8f8a9380@redhat.com> <871ro52ary.fsf@x220.int.ebiederm.org> <373a6898-4020-4af1-5b3d-f827d705dd77@redhat.com> <875zdg26hp.fsf@x220.int.ebiederm.org> <20200430152403.e0d6da5eb1cad06411ac6d46@linux-foundation.org> <5c908ec3-9495-531e-9291-cbab24f292d6@redhat.com> From: David Hildenbrand Message-ID: <2d019c11-a478-9d70-abd5-4fd2ebf4bc1d@redhat.com> Date: Fri, 1 May 2020 19:21:15 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Sender: linux-s390-owner@vger.kernel.org List-ID: To: Dan Williams Cc: Andrew Morton , "Eric W. Biederman" , Linux Kernel Mailing List , Linux MM , virtio-dev@lists.oasis-open.org, virtualization@lists.linux-foundation.org, linuxppc-dev , Linux ACPI , linux-nvdimm , linux-hyperv@vger.kernel.org, linux-s390 , xen-devel , Michal Hocko , "Michael S . Tsirkin" , Michal Hocko , Pankaj Gupta , Wei Yang , Baoquan He On 01.05.20 18:56, Dan Williams wrote: > On Fri, May 1, 2020 at 2:34 AM David Hildenbrand wro= te: >> >> On 01.05.20 00:24, Andrew Morton wrote: >>> On Thu, 30 Apr 2020 20:43:39 +0200 David Hildenbrand wrote: >>> >>>>> >>>>> Why does the firmware map support hotplug entries? >>>> >>>> I assume: >>>> >>>> The firmware memmap was added primarily for x86-64 kexec (and still,= is >>>> mostly used on x86-64 only IIRC). There, we had ACPI hotplug. When D= IMMs >>>> get hotplugged on real HW, they get added to e820. Same applies to >>>> memory added via HyperV balloon (unless memory is unplugged via >>>> ballooning and you reboot ... the the e820 is changed as well). I as= sume >>>> we wanted to be able to reflect that, to make kexec look like a real= reboot. >>>> >>>> This worked for a while. Then came dax/kmem. Now comes virtio-mem. >>>> >>>> >>>> But I assume only Andrew can enlighten us. >>>> >>>> @Andrew, any guidance here? Should we really add all memory to the >>>> firmware memmap, even if this contradicts with the existing >>>> documentation? (especially, if the actual firmware memmap will *not* >>>> contain that memory after a reboot) >>> >>> For some reason that patch is misattributed - it was authored by >>> Shaohui Zheng , who hasn't been heard from i= n >>> a decade. I looked through the email discussion from that time and I= 'm >>> not seeing anything useful. But I wasn't able to locate Dave Hansen'= s >>> review comments. >> >> Okay, thanks for checking. I think the documentation from 2008 is pret= ty >> clear what has to be done here. I will add some of these details to th= e >> patch description. >> >> Also, now that I know that esp. kexec-tools already don't consider >> dax/kmem memory properly (memory will not get dumped via kdump) and >> won't really suffer from a name change in /proc/iomem, I will go back = to >> the MHP_DRIVER_MANAGED approach and >> 1. Don't create firmware memmap entries >> 2. Name the resource "System RAM (driver managed)" >> 3. Flag the resource via something like IORESOURCE_MEM_DRIVER_MANAGED. >> >> This way, kernel users and user space can figure out that this memory >> has different semantics and handle it accordingly - I think that was >> what Eric was asking for. >> >> Of course, open for suggestions. >=20 > I'm still more of a fan of this being communicated by "System RAM" I was mentioning somewhere in this thread that "System RAM" inside a hierarchy (like dax/kmem) will already be basically ignored by kexec-tools. So, placing it inside a hierarchy already makes it look special already. But after all, as we have to change kexec-tools either way, we can directly go ahead and flag it properly as special (in case there will ever be other cases where we could no longer distinguish it). > being parented especially because that tells you something about how > the memory is driver-managed and which mechanism might be in play. The could be communicated to some degree via the resource hierarchy. E.g., [root@localhost ~]# cat /proc/iomem ... 140000000-33fffffff : Persistent Memory 140000000-1481fffff : namespace0.0 150000000-33fffffff : dax0.0 150000000-33fffffff : System RAM (driver managed) vs. :/# cat /proc/iomem [...] 140000000-333ffffff : virtio-mem (virtio0) 140000000-147ffffff : System RAM (driver managed) 148000000-14fffffff : System RAM (driver managed) 150000000-157ffffff : System RAM (driver managed) Good enough for my taste. > What about adding an optional /sys/firmware/memmap/X/parent attribute. I really don't want any firmware memmap entries for something that is not part of the firmware provided memmap. In addition, /sys/firmware/memmap/ is still a fairly x86_64 specific thing. Only mips and two arm configs enable it at all. So, IMHO, /sys/firmware/memmap/ is definitely not the way to go. --=20 Thanks, David / dhildenb