search for: walk_system_ram_range

...s) == flags checks that all "flags" are set (additional ones might be set). !(cur->flags & ~flags) checks that no other flags besides "flags" are set (and "flags" are not required to be set). We use the same handling in find_next_iomem_res(), e.g., called via walk_system_ram_range also with IORESOURCE_SYSTEM_RAM | IORESOURCE_BUSY. Thanks for having a look! -- Thanks, David / dhildenb

This is the follow-up of "[PATCH RFCv1 0/5] mm/memory_hotplug: selective merging of memory resources" [1] 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