On Thu, Apr 30, 2020 at 11:44 AM David Hildenbrand <david(a)redhat.com> wrote:
>>> If the class of memory is different then please by all means let's
>>> it differently in struct resource so everyone knows it is different.
>>> But that difference needs to be more than hotplug.
>>> That difference needs to be the hypervisor loaned us memory and might
>>> take it back at any time, or this memory is persistent and so it has
>>> these different characteristics so don't use it as ordinary ram.
>> Yes, and I think kmem took an excellent approach of explicitly putting
>> that "System RAM" into a resource hierarchy. That "System
>> show up as a root node under /proc/iomem (see patch #3), which already
>> results in kexec-tools to treat it in a special way. I am thinking about
>> doing the same for virtio-mem.
> Reading this and your patch cover letters again my concern is that
> the justification seems to be letting the tail wag the dog.
> You want kexec-tools to behave in a certain way so you are changing the
> Rather it should be change the kernel to clearly reflect reality and if
> you can get away without a change to kexec-tools that is a bonus.
Right, because user space has to have a way to figure out what to do.
But talking about the firmware memmap, indicating something via a "raw
firmware-provided memory map", that is not actually in the "raw
firmware-provided memory map" feels wrong to me. (below)
>>> That information is also useful to other people looking at the system
>>> and seeing what is going on.
>>> Just please don't muddle the concepts, or assume that whatever subset
>>> hotplug memory you are dealing with is the only subset.
>> I can certainly rephrase the subject/description/comment, stating that
>> this is not to be used for ordinary hotplugged DIMMs - only when the
>> device driver is under control to decide what to do with that memory -
>> especially when kexec'ing.
>> (previously, I called this flag MHP_DRIVER_MANAGED, but I think
>> MHP_NO_FIRMWARE_MEMMAP is clearer, we just need a better description)
>> Would that make it clearer?
> I am not certain, but Andrew Morton deliberately added that
> firmware_map_add_hotplug call. Which means that there is a reason
> for putting hotplugged memory in the firmware map.
> So the justification needs to take that reason into account. The
> justification can not be it is hotplugged therefore it should not belong
> in the firmware memory map. Unless you can show that
> firmware_map_add_hotplug that was actually a bug and should be removed.
> But as it has been that way since 2010 that seems like a long shot.
> So my question is what is right for the firmware map?
We have documentation for that since 2008. Andrews patch is from 2010.
It clearly talks about "raw firmware-provided memory map" and why the
interface was introduced at all ("on most architectures that
firmware-provided memory map is modified afterwards by the kernel itself").
> Why does the firmware map support hotplug entries?
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 DIMMs
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 assume
we wanted to be able to reflect that, to make kexec look like a real reboot.
I can at least say that this breakdown makes sense to me. Traditional
memory hotplug results in permanent change to the raw firmware memory
map reported by the host at next reboot. These device-driver-owned
memory regions really want a hotplug policy per-kernel boot instance
and should fall back to the default reserved state at reboot (kexec or
otherwise). When I say hotplug-policy I mean whether the current
kernel wants to treat the device range as System RAM or leave it as
device-managed. The intent is that the follow-on kernel needs to
re-decide the device policy.
> This worked for a while. Then came dax/kmem. Now comes virtio-mem.