DepSurf

Function: kvm_arch_mmu_notifier_invalidate_range

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: ✅

  int kvm_arch_mmu_notifier_invalidate_range(struct kvm *kvm, long unsigned int start, long unsigned int end, bool blockable);
  

  Collision: Unique Global

  Inline: No

  Transformation: False

  Instances:

  In virt/kvm/kvm_main.c (ffff8000100bb3e8)
  Location: virt/kvm/kvm_main.c:160
  Inline: False
  Direct callers:
    - virt/kvm/kvm_main.c:kvm_mmu_notifier_invalidate_range_start
  

  Symbols:

  ffff8000100bb3e8-ffff8000100bb404: kvm_arch_mmu_notifier_invalidate_range (STB_WEAK)
  

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

Flavor

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

Differences

Arch