search for: 33fffffff

...kernel (loaded via kexec_load()). The memory will be considered initial System RAM by the kexec kernel. We should let the kexec kernel decide how to use that memory - just as we do during an ordinary reboot. Before configuring the namespace: [root at localhost ~]# cat /proc/iomem ... 140000000-33fffffff : Persistent Memory 140000000-33fffffff : namespace0.0 3280000000-32ffffffff : PCI Bus 0000:00 After configuring the namespace: [root at localhost ~]# cat /proc/iomem ... 140000000-33fffffff : Persistent Memory 140000000-1481fffff : namespace0.0 148200000-33fffffff : dax0.0 328000000...

This is the follow up of [1]: [PATCH v1 0/3] mm/memory_hotplug: Make virtio-mem play nicely with kexec-tools I realized that this is not only helpful for virtio-mem, but also for dax/kmem - it's a fix for that use case (see patch #3) of persistent memory. Also, while testing, I discovered that kexec-tools will *not* add dax/kmem memory (anything not directly under the root when parsing

...omething 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 at 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-3...

...omething 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 at 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-3...

...ich mechanism might be in play. >>> >>> The could be communicated to some degree via the resource hierarchy. >>> >>> E.g., >>> >>> [root at 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/i...

...ich mechanism might be in play. >>> >>> The could be communicated to some degree via the resource hierarchy. >>> >>> E.g., >>> >>> [root at 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/i...

On Fri, May 1, 2020 at 2:34 AM David Hildenbrand <david at redhat.com> wrote: > > On 01.05.20 00: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

On Fri, May 1, 2020 at 2:34 AM David Hildenbrand <david at redhat.com> wrote: > > On 01.05.20 00: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

...;>> The could be communicated to some degree via the resource hierarchy. >>>>> >>>>> E.g., >>>>> >>>>> [root at localhost ~]# cat /proc/iomem >>>>> ... >>>>> 140000000-33fffffff : Persistent Memory >>>>> 140000000-1481fffff : namespace0.0 >>>>> 150000000-33fffffff : dax0.0 >>>>> 150000000-33fffffff : System RAM (driver managed) >>>>> >>>>> vs. >>>...

...;>> The could be communicated to some degree via the resource hierarchy. >>>>> >>>>> E.g., >>>>> >>>>> [root at localhost ~]# cat /proc/iomem >>>>> ... >>>>> 140000000-33fffffff : Persistent Memory >>>>> 140000000-1481fffff : namespace0.0 >>>>> 150000000-33fffffff : dax0.0 >>>>> 150000000-33fffffff : System RAM (driver managed) >>>>> >>>>> vs. >>>...

...rented 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 at 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)...

...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 at 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 >> [....

...s on this memory), and it is exposed as "System RAM (virtio_mem)" in /proc/iomem, so esp. kexec-tools can properly handle it. Example /proc/iomem before this change: [...] 140000000-333ffffff : virtio0 140000000-147ffffff : System RAM 334000000-533ffffff : virtio1 338000000-33fffffff : System RAM 340000000-347ffffff : System RAM 348000000-34fffffff : System RAM [...] Example /proc/iomem after this change: [...] 140000000-333ffffff : virtio0 140000000-147ffffff : System RAM (virtio_mem) 334000000-533ffffff : virtio1 338000000-33fffffff : System RAM (virt...

...s on this memory), and it is exposed as "System RAM (virtio_mem)" in /proc/iomem, so esp. kexec-tools can properly handle it. Example /proc/iomem before this change: [...] 140000000-333ffffff : virtio0 140000000-147ffffff : System RAM 334000000-533ffffff : virtio1 338000000-33fffffff : System RAM 340000000-347ffffff : System RAM 348000000-34fffffff : System RAM [...] Example /proc/iomem after this change: [...] 140000000-333ffffff : virtio0 140000000-147ffffff : System RAM (virtio_mem) 334000000-533ffffff : virtio1 338000000-33fffffff : System RAM (virt...

...ee via the resource hierarchy. >>>>>>> >>>>>>> E.g., >>>>>>> >>>>>>> [root at localhost ~]# cat /proc/iomem >>>>>>> ... >>>>>>> 140000000-33fffffff : Persistent Memory >>>>>>> 140000000-1481fffff : namespace0.0 >>>>>>> 150000000-33fffffff : dax0.0 >>>>>>> 150000000-33fffffff : System RAM (driver managed) >>>>>>> >&...

...ee via the resource hierarchy. >>>>>>> >>>>>>> E.g., >>>>>>> >>>>>>> [root at localhost ~]# cat /proc/iomem >>>>>>> ... >>>>>>> 140000000-33fffffff : Persistent Memory >>>>>>> 140000000-1481fffff : namespace0.0 >>>>>>> 150000000-33fffffff : dax0.0 >>>>>>> 150000000-33fffffff : System RAM (driver managed) >>>>>>> >&...

...;>> > >>> The could be communicated to some degree via the resource hierarchy. > >>> > >>> E.g., > >>> > >>> [root at localhost ~]# cat /proc/iomem > >>> ... > >>> 140000000-33fffffff : Persistent Memory > >>> 140000000-1481fffff : namespace0.0 > >>> 150000000-33fffffff : dax0.0 > >>> 150000000-33fffffff : System RAM (driver managed) > >>> > >>> vs. > >>> > >...

...cated to some degree via the resource hierarchy. > >>>>> > >>>>> E.g., > >>>>> > >>>>> [root at localhost ~]# cat /proc/iomem > >>>>> ... > >>>>> 140000000-33fffffff : Persistent Memory > >>>>> 140000000-1481fffff : namespace0.0 > >>>>> 150000000-33fffffff : dax0.0 > >>>>> 150000000-33fffffff : System RAM (driver managed) > >>>>> > >>>...

...kes /proc/iomem explode in size (e.g., requiring kexec-tools to manually merge resources later when e.g., trying to create a kdump header). Before this patch, we get (/proc/iomem) when hotplugging 2G via virtio-mem on x86-64: [...] 100000000-13fffffff : System RAM 140000000-33fffffff : virtio0 140000000-147ffffff : System RAM (virtio_mem) 148000000-14fffffff : System RAM (virtio_mem) 150000000-157ffffff : System RAM (virtio_mem) 158000000-15fffffff : System RAM (virtio_mem) 160000000-167ffffff : System RAM (virtio_mem)...

...> >>>>>>> > >>>>>>> E.g., > >>>>>>> > >>>>>>> [root at localhost ~]# cat /proc/iomem > >>>>>>> ... > >>>>>>> 140000000-33fffffff : Persistent Memory > >>>>>>> 140000000-1481fffff : namespace0.0 > >>>>>>> 150000000-33fffffff : dax0.0 > >>>>>>> 150000000-33fffffff : System RAM (driver managed) > >>>&g...