From: David Hildenbrand <david@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Michael S . Tsirkin" <mst@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
David Gibson <david@gibson.dropbear.id.au>,
Eduardo Habkost <ehabkost@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
David Hildenbrand <david@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/7] qapi/range/memory-device: fixes and cleanups
Date: Fri, 12 Oct 2018 13:49:09 +0200 [thread overview]
Message-ID: <20181012114916.23532-1-david@redhat.com> (raw)
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.
v1 -> v2:
- "range: add some more functions"
-- Reduce number of functions
-- make range_init() return an error in case of overflow
-- provide range_init_nofail()
- "memory-device: rewrite address assignment using ranges"
-- Use new functions range_init/range_init_nofail
-- Use range_contains_range instead of starts_before/ends_after
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 | 60 +++++++++-------
include/qemu/range.h | 68 +++++++++++++++++-
qapi/string-input-visitor.c | 133 ++++++++++++++++++++++++++++++------
3 files changed, 210 insertions(+), 51 deletions(-)
--
2.17.1
next reply other threads:[~2018-10-12 11:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 11:49 David Hildenbrand [this message]
2018-10-12 11:49 ` [Qemu-devel] [PATCH v2 1/7] qapi: correctly parse uint64_t values from strings David Hildenbrand
2018-10-17 12:42 ` Markus Armbruster
2018-10-23 12:10 ` David Hildenbrand
2018-10-23 15:07 ` David Hildenbrand
2018-10-12 11:49 ` [Qemu-devel] [PATCH v2 2/7] qapi: use qemu_strtoi64() in parse_str_int64 David Hildenbrand
2018-10-12 11:49 ` [Qemu-devel] [PATCH v2 3/7] range: pass const pointer where possible David Hildenbrand
2018-10-12 11:49 ` [Qemu-devel] [PATCH v2 4/7] range: add some more functions David Hildenbrand
2018-10-12 11:49 ` [Qemu-devel] [PATCH v2 5/7] memory-device: use QEMU_IS_ALIGNED David Hildenbrand
2018-10-12 11:49 ` [Qemu-devel] [PATCH v2 6/7] memory-device: avoid overflows on very huge devices David Hildenbrand
2018-10-12 11:49 ` [Qemu-devel] [PATCH v2 7/7] memory-device: rewrite address assignment using ranges David Hildenbrand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181012114916.23532-1-david@redhat.com \
--to=david@redhat.com \
--cc=armbru@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.