search for: 147ffffff

Displaying 20 results from an estimated 35 matches for "147ffffff".

[PATCH v1] virtio-mem: add memory via add_memory_driver_managed()
2020 Jun 11
2
[PATCH v1] virtio-mem: add memory via add_memory_driver_managed()
...EM_DRIVER_MANAGED (esp., kexec_file_load() will not place kexec images 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) 334...
[PATCH v1] virtio-mem: add memory via add_memory_driver_managed()
2020 Jun 11
2
[PATCH v1] virtio-mem: add memory via add_memory_driver_managed()
...EM_DRIVER_MANAGED (esp., kexec_file_load() will not place kexec images 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) 334...
[PATCH v1] virtio-mem: add memory via add_memory_driver_managed()
2020 Jun 11
0
[PATCH v1] virtio-mem: add memory via add_memory_driver_managed()
..._load() will not place > kexec images 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 > 1...
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
2020 May 01
2
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
...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. > >...
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
2020 May 01
2
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
...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. > >...
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
2020 May 01
2
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
...t;>> 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 /sy...
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
2020 May 01
2
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
...t;>> 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 /sy...
[PATCH v1 2/3] mm/memory_hotplug: Introduce MHP_DRIVER_MANAGED
2020 Apr 30
1
[PATCH v1 2/3] mm/memory_hotplug: Introduce MHP_DRIVER_MANAGED
...that's already done) E.g., regarding virtio-mem (patch #3) I am currently also looking into creating a parent resource instead, like dax/kmem to avoid the rename: :/# cat /proc/iomem 00000000-00000fff : Reserved [...] 100000000-13fffffff : System RAM 140000000-33fffffff : virtio0 140000000-147ffffff : System RAM 148000000-14fffffff : System RAM 150000000-157ffffff : System RAM 340000000-303fffffff : virtio1 340000000-347ffffff : System RAM 3280000000-32ffffffff : PCI Bus 0000:00 -- Thanks, David / dhildenb
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
2020 May 01
2
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
...t;>>>>> 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....
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
2020 May 01
2
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
...t;>>>>> 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....
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
2020 May 01
2
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
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
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
2020 May 01
2
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
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
[PATCH RFCv1 3/5] virtio-mem: try to merge "System RAM (virtio_mem)" resources
2020 Jul 31
0
[PATCH RFCv1 3/5] virtio-mem: try to merge "System RAM (virtio_mem)" resources
...equiring 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) 168000000-16fffffff : System RAM (virti...
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
2020 May 01
2
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
...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. >>>>> >>&g...
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
2020 May 01
2
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
...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. >>>>> >>&g...
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
2020 May 01
0
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
...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...
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
2020 May 01
0
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
...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/pare...
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
2020 May 01
0
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
...0-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. > >>> > >>>> Wha...
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
2020 May 01
2
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
...gt;>>>>> >>>>>>>>> :/# 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) >>>>>>>>> >>>>>>>&g...
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
2020 May 01
2
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
...gt;>>>>> >>>>>>>>> :/# 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) >>>>>>>>> >>>>>>>&g...