aboutsummaryrefslogtreecommitdiff
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorAlexander Bulekov <alxndr@bu.edu>2021-03-15 10:05:10 -0400
committerPaolo Bonzini <pbonzini@redhat.com>2021-03-16 14:30:30 -0400
commit230376d285b38f5b83882ebdd2e0d0570431dd09 (patch)
treeab179fb04da2c021b4e140879185a612c772db56 /MAINTAINERS
parentd7da0e560128e56f55a2f1f27fa66dd8c5db446c (diff)
downloadqemu-230376d285b38f5b83882ebdd2e0d0570431dd09.zip
qemu-230376d285b38f5b83882ebdd2e0d0570431dd09.tar.gz
qemu-230376d285b38f5b83882ebdd2e0d0570431dd09.tar.bz2
memory: add a sparse memory device for fuzzing
For testing, it can be useful to simulate an enormous amount of memory (e.g. 2^64 RAM). This adds an MMIO device that acts as sparse memory. When something writes a nonzero value to a sparse-mem address, we allocate a block of memory. For now, since the only user of this device is the fuzzer, we do not track and free zeroed blocks. The device has a very low priority (so it can be mapped beneath actual RAM, and virtual device MMIO regions). Signed-off-by: Alexander Bulekov <alxndr@bu.edu> Reviewed-by: Darren Kenny <darren.kenny@oracle.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'MAINTAINERS')
-rw-r--r--MAINTAINERS1
1 files changed, 1 insertions, 0 deletions
diff --git a/MAINTAINERS b/MAINTAINERS
index 0bd720a..2a925e7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2636,6 +2636,7 @@ S: Maintained
F: tests/qtest/fuzz/
F: tests/qtest/fuzz-*test.c
F: scripts/oss-fuzz/
+F: hw/mem/sparse-mem.c
F: docs/devel/fuzzing.rst
Register API