search for: memmap

...;>>>>>>>>>>> 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 DIMMs >>>>>>>>>>> get hotplugged on real HW, they get added to e820. Same applies to >>>>&...

...;>>>>>>>>>>> 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 DIMMs >>>>>>>>>>> get hotplugged on real HW, they get added to e820. Same applies to >>>>&...

...>>>>>>>>> >>>>>>>>>> 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 DIMMs >>>>>>>>> get hotplugged on real HW, they get added to e820. Same applies to >>>>>>>>&...

...>>>>>>>>> >>>>>>>>>> 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 DIMMs >>>>>>>>> get hotplugged on real HW, they get added to e820. Same applies to >>>>>>>>&...

...hat.com> 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 DIMMs >>>>>>> get hotplugged on real HW, they get added to e820. Same applies to >>>>>>> memory added via Hyp...

...hat.com> 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 DIMMs >>>>>>> get hotplugged on real HW, they get added to e820. Same applies to >>>>>>> memory added via Hyp...

...;>>> 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 DIMMs >>>>>>>>>>>>> get hotplugged on real HW, they get added to e820. Same applies to &...

...;>>> 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 DIMMs >>>>>>>>>>>>> get hotplugged on real HW, they get added to e820. Same applies to &...

On 29.04.20 18:08, David Hildenbrand wrote: > Some paravirtualized devices that add memory via add_memory() and > friends (esp. virtio-mem) don't want to create entries in > /sys/firmware/memmap/ - primarily to hinder kexec from adding this > memory to the boot memmap of the kexec kernel. > > In fact, such memory is never exposed via the firmware (e.g., e820), but > only via the device, so exposing this memory via /sys/firmware/memmap/ is > wrong: > "kexec needs th...

On 29.04.20 18:08, David Hildenbrand wrote: > Some paravirtualized devices that add memory via add_memory() and > friends (esp. virtio-mem) don't want to create entries in > /sys/firmware/memmap/ - primarily to hinder kexec from adding this > memory to the boot memmap of the kexec kernel. > > In fact, such memory is never exposed via the firmware (e.g., e820), but > only via the device, so exposing this memory via /sys/firmware/memmap/ is > wrong: > "kexec needs th...

...20:43:39 +0200 David Hildenbrand <david at redhat.com> 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 DIMMs > >>>> get hotplugged on real HW, they get added to e820. Same applies to > >>>> memory added via HyperV balloon (unless m...

...20:43:39 +0200 David Hildenbrand <david at redhat.com> 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 DIMMs > >>>> get hotplugged on real HW, they get added to e820. Same applies to > >>>> memory added via HyperV balloon (unless m...

...AM David Hildenbrand <david at redhat.com> wrote: >> >> On 29.04.20 18:08, David Hildenbrand wrote: >>> Some paravirtualized devices that add memory via add_memory() and >>> friends (esp. virtio-mem) don't want to create entries in >>> /sys/firmware/memmap/ - primarily to hinder kexec from adding this >>> memory to the boot memmap of the kexec kernel. >>> >>> In fact, such memory is never exposed via the firmware (e.g., e820), but >>> only via the device, so exposing this memory via /sys/firmware/memmap/ is >&gt...

...:24, Andrew Morton wrote: > > On Thu, 30 Apr 2020 20:43:39 +0200 David Hildenbrand <david at redhat.com> 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 DIMMs > >> get hotplugged on real HW, they get added to e820. Same applies to > >> memory added via HyperV balloon (unless memory is unplugged via &...

...:24, Andrew Morton wrote: > > On Thu, 30 Apr 2020 20:43:39 +0200 David Hildenbrand <david at redhat.com> 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 DIMMs > >> get hotplugged on real HW, they get added to e820. Same applies to > >> memory added via HyperV balloon (unless memory is unplugged via &...

David Hildenbrand <david at redhat.com> writes: > Some devices/drivers that add memory via add_memory() and friends (e.g., > dax/kmem, but also virtio-mem in the future) don't want to create entries > in /sys/firmware/memmap/ - primarily to hinder kexec from adding this > memory to the boot memmap of the kexec kernel. > > In fact, such memory is never exposed via the firmware memmap as System > RAM (e.g., e820), so exposing this memory via /sys/firmware/memmap/ is > wrong: > "kexec needs the raw...

David Hildenbrand <david at redhat.com> writes: > Some devices/drivers that add memory via add_memory() and friends (e.g., > dax/kmem, but also virtio-mem in the future) don't want to create entries > in /sys/firmware/memmap/ - primarily to hinder kexec from adding this > memory to the boot memmap of the kexec kernel. > > In fact, such memory is never exposed via the firmware memmap as System > RAM (e.g., e820), so exposing this memory via /sys/firmware/memmap/ is > wrong: > "kexec needs the raw...

...;>>>>>> 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 DIMMs > >>>>>>>>>>> get hotplugged on real HW, they get added to e820. Same applies to > &g...

...gt;>> > >>>>>>>>>> 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 DIMMs > >>>>>>>>> get hotplugged on real HW, they get added to e820. Same applies to > >>>>&g...

...ing not directly under the root when parsing /proc/iomem) to the elfcorehdr, so this memory will never get included in a dump. This probably has to be fixed in kexec-tools - virtio-mem will require this as well. v1 -> v2: - Don't change the resource name - Rename the flag to MHP_NO_FIRMWARE_MEMMAP to reflect what it is doing - Rephrase subjects/descriptions - Use the flag for dax/kmem I'll have to rebase virtio-mem on these changes, there will be a resend. [1] https://lkml.kernel.org/r/20200429160803.109056-1-david at redhat.com David Hildenbrand (3): mm/memory_hotplug: Prepare pass...