summaryrefslogtreecommitdiffstats
path: root/softmmu/memory.c
diff options
context:
space:
mode:
authorAlexander Bulekov2021-03-15 15:05:11 +0100
committerPaolo Bonzini2021-03-16 19:30:30 +0100
commit25d309fb0d6c07e49c3d9250cdbacc16941d988e (patch)
tree48d36634c66bd2a1ae63de07156c25a726b6f558 /softmmu/memory.c
parentmemory: add a sparse memory device for fuzzing (diff)
downloadqemu-25d309fb0d6c07e49c3d9250cdbacc16941d988e.tar.gz
qemu-25d309fb0d6c07e49c3d9250cdbacc16941d988e.tar.xz
qemu-25d309fb0d6c07e49c3d9250cdbacc16941d988e.zip
fuzz: configure a sparse-mem device, by default
The generic-fuzzer often provides randomized DMA addresses to virtual-devices. For a 64-bit address-space, the chance of these randomized addresses coinciding with RAM regions, is fairly small. Even though the fuzzer's instrumentation eventually finds valid addresses, this can take some-time, and slows-down fuzzing progress (especially, when multiple DMA buffers are involved). To work around this, create "fake" sparse-memory that spans all of the 64-bit address-space. Adjust the DMA call-back to populate this sparse memory, correspondingly 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 'softmmu/memory.c')
0 files changed, 0 insertions, 0 deletions