[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [PATCH v1 0/7] qapi/range/memory-device: fixes and cleanups
From: |
David Hildenbrand |
Subject: |
[Qemu-devel] [PATCH v1 0/7] qapi/range/memory-device: fixes and cleanups |
Date: |
Tue, 9 Oct 2018 22:56:45 +0200 |
While working on memory device code, I noticed that specifiying an uint64_t
on command line does not work in all cases as we always parse an int64_t.
So I fix that and also cleanup the old int64_t parser.
To be able to fix some overflows in memory-device code in a clean way,
I am reusing the range implementation of qemu, for which I need some
more helpers.
This series is based on
"[PATCH v5 00/16] memory-device: complete refactoring"
which should get merged soon.
David Hildenbrand (7):
qapi: correctly parse uint64_t values from strings
qapi: use qemu_strtoi64() in parse_str_int64
range: pass const pointer where possible
range: add some more functions
memory-device: use QEMU_IS_ALIGNED
memory-device: avoid overflows on very huge devices
memory-device: rewrite address assignment using ranges
hw/mem/memory-device.c | 63 ++++++++++-------
include/qemu/range.h | 86 ++++++++++++++++++++++-
qapi/string-input-visitor.c | 133 ++++++++++++++++++++++++++++++------
3 files changed, 231 insertions(+), 51 deletions(-)
--
2.17.1
- [Qemu-devel] [PATCH v1 0/7] qapi/range/memory-device: fixes and cleanups,
David Hildenbrand <=