From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36280) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gAvwh-0002uU-3J for qemu-devel@nongnu.org; Fri, 12 Oct 2018 07:49:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gAvwd-0008GO-Kx for qemu-devel@nongnu.org; Fri, 12 Oct 2018 07:49:30 -0400 Received: from mx1.redhat.com ([209.132.183.28]:40849) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gAvwd-0008Bm-Eu for qemu-devel@nongnu.org; Fri, 12 Oct 2018 07:49:27 -0400 From: David Hildenbrand Date: Fri, 12 Oct 2018 13:49:09 +0200 Message-Id: <20181012114916.23532-1-david@redhat.com> Subject: [Qemu-devel] [PATCH v2 0/7] qapi/range/memory-device: fixes and cleanups List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: "Michael S . Tsirkin" , Igor Mammedov , Markus Armbruster , Michael Roth , David Gibson , Eduardo Habkost , "Dr . David Alan Gilbert" , David Hildenbrand 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