diff options
author | Michael Tokarev <mjt@tls.msk.ru> | 2012-06-07 20:08:19 +0400 |
---|---|---|
committer | Michael Tokarev <mjt@tls.msk.ru> | 2012-06-07 21:09:46 +0400 |
commit | 2278a69e7020d86a8c73a28474e7709d3e7d5081 (patch) | |
tree | 39682b4ed6dfc6d07bcc8e5dee45795999d2aafe /migration-unix.c | |
parent | dcf6f5e15ecee4f593eeacbe0591c1addc004d92 (diff) | |
download | hqemu-2278a69e7020d86a8c73a28474e7709d3e7d5081.zip hqemu-2278a69e7020d86a8c73a28474e7709d3e7d5081.tar.gz |
rewrite iov_* functions
This changes implementations of all iov_*
functions, completing the previous step.
All iov_* functions now ensure that this offset
argument is within the iovec (using assertion),
but lets to specify `bytes' value larger than
actual length of the iovec - in this case they
stops at the actual end of iovec. It is also
suggested to use convinient `-1' value as `bytes'
to mean just this -- "up to the end".
There's one very minor semantic change here: new
requiriment is that `offset' points to inside of
iovec. This is checked just at the end of functions
(assert()), it does not actually need to be enforced,
but using any of these functions with offset pointing
past the end of iovec is wrong anyway.
Note: the new code in iov.c uses arithmetic with
void pointers. I thought this is not supported
everywhere and is a GCC extension (indeed, the C
standard does not define void arithmetic). However,
the original code already use void arith in
iov_from_buf() function:
(memcpy(..., buf + buf_off,...)
which apparently works well so far (it is this
way in qemu 1.0). So I left it this way and used
it in other places.
While at it, add a unit-test file test-iov.c,
to check various corner cases with iov_from_buf(),
iov_to_buf() and iov_memset().
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
Diffstat (limited to 'migration-unix.c')
0 files changed, 0 insertions, 0 deletions