diff options
| author | Linus Torvalds <[email protected]> | 2021-11-13 13:14:05 -0800 | 
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2021-11-13 13:14:05 -0800 | 
| commit | ccfff0a2bd2a30de130b5623d242ddecd0272bc2 (patch) | |
| tree | f8350ca2054e1f6350cc4a308d08c60b5fa59a94 /tools/perf/scripts/python/Perf-Trace-Util/lib | |
| parent | 3ad7befd4842afa2449026715987122a1c6dcb85 (diff) | |
| parent | 61082ad6a6e1f999eef7e7e90046486c87933b1e (diff) | |
Merge tag 'virtio-mem-for-5.16' of git://github.com/davidhildenbrand/linux
Pull virtio-mem update from David Hildenbrand:
 "Support the VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE feature in virtio-mem,
  now that "accidential" access to logically unplugged memory inside
  added Linux memory blocks is no longer possible, because we:
   - Removed /dev/kmem in commit bbcd53c96071 ("drivers/char: remove
     /dev/kmem for good")
   - Disallowed access to virtio-mem device memory via /dev/mem in
     commit 2128f4e21aa ("virtio-mem: disallow mapping virtio-mem memory
     via /dev/mem")
   - Sanitized access to virtio-mem device memory via /proc/kcore in
     commit 0daa322b8ff9 ("fs/proc/kcore: don't read offline sections,
     logically offline pages and hwpoisoned pages")
   - Sanitized access to virtio-mem device memory via /proc/vmcore in
     commit ce2814622e84 ("virtio-mem: kdump mode to sanitize
     /proc/vmcore access")
  The new VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE feature that will be
  required by some hypervisors implementing virtio-mem in the near
  future, so let's support it now that we safely can"
* tag 'virtio-mem-for-5.16' of git://github.com/davidhildenbrand/linux:
  virtio-mem: support VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE
Diffstat (limited to 'tools/perf/scripts/python/Perf-Trace-Util/lib')
0 files changed, 0 insertions, 0 deletions