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> |
||
---|---|---|
.. | ||
fork_fuzz.c | ||
fork_fuzz.h | ||
fork_fuzz.ld | ||
fuzz.c | ||
fuzz.h | ||
generic_fuzz.c | ||
generic_fuzz_configs.h | ||
i440fx_fuzz.c | ||
meson.build | ||
qos_fuzz.c | ||
qos_fuzz.h | ||
qtest_wrappers.c | ||
virtio_blk_fuzz.c | ||
virtio_net_fuzz.c | ||
virtio_scsi_fuzz.c |