DepSurf

Function: __vmemmap_can_optimize

Status

Regular

• In 4.4: Absent ⚠️
• In 4.8: Absent ⚠️
• In 4.10: Absent ⚠️
• In 4.13: Absent ⚠️
• In 4.15: Absent ⚠️
• In 4.18: Absent ⚠️
• In 5.0: Absent ⚠️
• In 5.3: Absent ⚠️
• In 5.4: Absent ⚠️
• In 5.8: Absent ⚠️
• In 5.11: Absent ⚠️
• In 5.13: Absent ⚠️
• In 5.15: Absent ⚠️
• In 5.19: Absent ⚠️
• In 6.2: Absent ⚠️
• In 6.5: Absent ⚠️
• In 6.8: Duplicate, Full Inline ⚠️

  Collision: Static Duplication

  Inline: Full

  Transformation: False

  Instances:

  In mm/mm_init.c (ffffffff82228983)
  Location: include/linux/mm.h:3902
  Inline: True
  Inline callers:
    - mm/mm_init.c:memmap_init_zone_device
  

  In mm/sparse-vmemmap.c (ffffffff822330bf)
  Location: include/linux/mm.h:3902
  Inline: True
  Inline callers:
    - mm/sparse-vmemmap.c:__populate_section_memmap
  

Arch

• In arm64: Absent ⚠️
• In armhf: Absent ⚠️
• In ppc64el: Absent ⚠️
• In riscv64: Absent ⚠️

Flavor

• In aws: Absent ⚠️
• In azure: Absent ⚠️
• In gcp: Absent ⚠️
• In lowlatency: Absent ⚠️

Differences