DepSurf

Function: is_fadump_mem_area_contiguous

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: Absent ⚠️

Arch

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

  bool is_fadump_mem_area_contiguous(u64 d_start, u64 d_end);
  

  Collision: Unique Static

  Inline: No

  Transformation: False

  Instances:

  In arch/powerpc/kernel/fadump.c (c00000000004be90)
  Location: arch/powerpc/kernel/fadump.c:165
  Inline: False
  Direct callers:
    - arch/powerpc/kernel/fadump.c:is_fadump_reserved_mem_contiguous
    - arch/powerpc/kernel/fadump.c:is_fadump_boot_mem_contiguous
  

  Symbols:

  c00000000004be90-c00000000004bf28: is_fadump_mem_area_contiguous (STB_LOCAL)
  

• In riscv64: Absent ⚠️

Flavor

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

Differences

Arch