diff options
| author | Paolo Bonzini <pbonzini@redhat.com> | 2016-05-23 14:54:06 +0200 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2016-05-25 19:04:11 +0200 |
| commit | 8a8e63ebdd5a6605af6a9df07c62b2214e1a650c (patch) | |
| tree | a6b6ee512647a71561ededbe29267ca2fa67cb18 /Changelog | |
| parent | cbe0ed6247a0589e4f72b25984b8afcfa9c26b1c (diff) | |
| download | qemu-8a8e63ebdd5a6605af6a9df07c62b2214e1a650c.zip qemu-8a8e63ebdd5a6605af6a9df07c62b2214e1a650c.tar.gz qemu-8a8e63ebdd5a6605af6a9df07c62b2214e1a650c.tar.bz2 | |
dma-helpers: change BlockBackend to opaque value in DMAIOFunc
Callers of dma_blk_io have no way to pass extra data to the DMAIOFunc,
because the original callback and opaque are gone by the time DMAIOFunc
is called. On the other hand, the BlockBackend is usually derived
from those extra data that you could pass to the DMAIOFunc (in the
next patch, that would be the SCSIRequest).
So change DMAIOFunc's prototype, decoupling it from blk_aio_readv
and blk_aio_writev's. The new prototype loses the BlockBackend
and gains an extra opaque value which, in the case of dma_blk_readv
and dma_blk_writev, is of course used for the BlockBackend.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'Changelog')
0 files changed, 0 insertions, 0 deletions