search for: 14fffffff

Displaying 20 results from an estimated 31 matches for "14fffffff".

Did you mean: 4fffffff
[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
...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 th...
[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
...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 th...
[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
...>>> >>> 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&...
[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
...>>> >>> 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&...
[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
...garding 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
...:/# 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...
[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
...:/# 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...
[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
...hen 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 (virtio_mem) 170000000-177ffffff : 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
...t; >>>>> :/# 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; >>>>> :/# 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
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/parent attribute. I really don't want any firmware memmap entries for something that is not part of the firmware p...
[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
...f : 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 memm...
[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
...> >>> > >>> :/# 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
...gt;>>>>>> [...] >>>>>>>>> 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. >>>>>>>>> >>>>>>>&gt...
[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;>>>>>> [...] >>>>>>>>> 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. >>>>>>>>> >>>>>>>&gt...
[PATCH RFCv1 0/5] mm/memory_hotplug: selective merging of memory resources
2020 Jul 31
6
[PATCH RFCv1 0/5] mm/memory_hotplug: selective merging of memory resources
Some add_memory*() users add memory in small, contiguous memory blocks. Examples include virtio-mem, hyper-v balloon, and the XEN balloon. This can quickly result in a lot of memory resources, whereby the actual resource boundaries are not of interest (e.g., it might be relevant for DIMMs, exposed via /proc/iomem to user space). We really want to merge added resources in this scenario where
[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
...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) > >>>>> > >>>>> Good enough for my taste. > >>>>> > >>>>>> What about adding an optional /sys/firmware/m...
[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
...em > >>>>>>> [...] > >>>>>>> 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...