Skip to content

access_process_vm device memory access

Rik van Riel lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest5 patches 4 repliesIn review

Changelog from the cover letter

- use CONFIG_HAVE_IOREMAP_PROT
- do not use generic_access_phys as a fallback but define it in the ->vm_ops->access for appropriate VMAs
- other code cleanups suggested by Andrew Morton and Sam Ravnborg

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/5access_process_vm device memory infrastructurearch/Kconfig arch/x86/Kconfig arch/x86/mm/ioremap.c +4 more+137 -182 replies
2/5use generic_access_phys for /dev/mem mappingsdrivers/char/mem.c+2 -10 replies
3/5use generic_access_phys for pci mmap on x86arch/x86/pci/i386.c+1 -00 replies
4/5powerpc ioremap_protarch/powerpc/Kconfig arch/powerpc/mm/pgtable_32.c arch/powerpc/mm/pgtable_64.c +4 more+64 -70 replies
5/5spufs use the new vm_ops->accessarch/powerpc/platforms/cell/spufs/file.c+23 -00 replies

Reviews trailers per patch

1 of 5 patches has a Reviewed-by or Acked-by.

PatchPeter Zijlstra
1/5A-b
2/5
3/5
4/5
5/5

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [patch 0/5] access_process_vm device memory access

In order to be able to debug things like the X server and programs using the PPC Cell SPUs, the debugger needs to be able to access device memory through ptrace and /proc/pid/mem.

Changelog:
- use CONFIG_HAVE_IOREMAP_PROT
- do not use generic_access_phys as a fallback but define it in the ->vm_ops->access for appropriate VMAs
- other code cleanups suggested by Andrew Morton and Sam Ravnborg

Signature · 1 line
All Rights Reversed