summaryrefslogtreecommitdiff
path: root/include/qemu/range.h
diff options
context:
space:
mode:
authorMichael S. Tsirkin <mst@redhat.com>2013-05-13 17:13:15 +0300
committerMichael S. Tsirkin <mst@redhat.com>2013-07-04 10:40:56 +0300
commit620ac82eb0fc4218fb6a4937bcef3fdab3126703 (patch)
treed914935f025c71e8ba2133c07af0a54faf8fbccc /include/qemu/range.h
parentab8bf29078e0ab8347e2ff8b4e5542f7a0c751cf (diff)
downloadqemu-620ac82eb0fc4218fb6a4937bcef3fdab3126703.tar.gz
range: add Range structure
Sometimes we need to pass ranges around, add a handy structure for this purpose. Note: memory.c defines its own concept of AddrRange structure for working with 128 addresses. It's necessary there for doing range math. This is not needed for most users: struct Range is much simpler, and is only used for passing the range around. Cc: Peter Maydell <peter.maydell@linaro.org> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'include/qemu/range.h')
-rw-r--r--include/qemu/range.h16
1 files changed, 16 insertions, 0 deletions
diff --git a/include/qemu/range.h b/include/qemu/range.h
index 350237212b..b76cc0df09 100644
--- a/include/qemu/range.h
+++ b/include/qemu/range.h
@@ -1,6 +1,22 @@
#ifndef QEMU_RANGE_H
#define QEMU_RANGE_H
+#include <inttypes.h>
+
+/*
+ * Operations on 64 bit address ranges.
+ * Notes:
+ * - ranges must not wrap around 0, but can include the last byte ~0x0LL.
+ * - this can not represent a full 0 to ~0x0LL range.
+ */
+
+/* A structure representing a range of addresses. */
+struct Range {
+ uint64_t begin; /* First byte of the range, or 0 if empty. */
+ uint64_t end; /* 1 + the last byte. 0 if range empty or ends at ~0x0LL. */
+};
+typedef struct Range Range;
+
/* Get last byte of a range from offset + length.
* Undefined for ranges that wrap around 0. */
static inline uint64_t range_get_last(uint64_t offset, uint64_t len)