search for: find_next_iomem_r

...on) kallsyms atomic_try_cmpxchg 1038 100.000 (no location information) kallsyms atomic_try_cmpxchg [self] ------------------------------------------------------------------------------- 990 0.1363 (no location information) kallsyms find_next_iomem_res 990 100.000 (no location information) kallsyms find_next_iomem_res [self] ------------------------------------------------------------------------------- 837 0.1152 (no location information) libc-2.30.so cfree at GLIBC_2.0 837 100.000 (no loc...

...--------------------------------------------------------------- 1661 0.3363 nouveau /nouveau 1661 100.000 nouveau /nouveau [self] ------------------------------------------------------------------------------- 1462 0.2960 kallsyms find_next_iomem_res 1462 100.000 kallsyms find_next_iomem_res [self] ------------------------------------------------------------------------------- 1355 0.2744 kvm_amd /kvm_amd 1355 100.000 kvm_amd /kvm_amd [self] --------------------------------...

...rent I think. (cur->flags & flags) == 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