[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC 2/6] OptsVisitor: introduce list modes for interva
From: |
Paolo Bonzini |
Subject: |
Re: [Qemu-devel] [RFC 2/6] OptsVisitor: introduce list modes for interval flattening |
Date: |
Thu, 18 Jul 2013 16:56:42 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 |
Il 18/07/2013 15:59, Laszlo Ersek ha scritto:
> The new modes are equal-rank, exclusive sub-modes of LM_IN_PROGRESS. Teach
> opts_next_list(), opts_type_int() and opts_type_uint64() to handle them.
Perhaps you could use a bitmap then:
LM_NONE = 0
LM_STARTED = 1
LM_IN_PROGRESS = 2
LM_SIGNED_INTERVAL = LM_IN_PROGRESS | 4
LM_UNSIGNED_INTERVAL = LM_IN_PROGRESS | 8
I think the only change would be that this hunk:
> @@ -211,7 +238,10 @@ opts_end_list(Visitor *v, Error **errp)
> {
> OptsVisitor *ov = DO_UPCAST(OptsVisitor, visitor, v);
>
> - assert(ov->list_mode == LM_STARTED || ov->list_mode == LM_IN_PROGRESS);
> + assert(ov->list_mode == LM_STARTED ||
> + ov->list_mode == LM_IN_PROGRESS ||
> + ov->list_mode == LM_SIGNED_INTERVAL ||
> + ov->list_mode == LM_UNSIGNED_INTERVAL);
> ov->repeated_opts = NULL;
> ov->list_mode = LM_NONE;
> }
could be changed to
assert(ov->list_mode == LM_STARTED ||
(ov->list_mode & LM_IN_PROGRESS));
Paolo
[Qemu-devel] [RFC 4/6] OptsVisitor: rebase opts_type_uint64() to parse_uint_full(), Laszlo Ersek, 2013/07/18
[Qemu-devel] [RFC 3/6] OptsVisitor: opts_type_int(): recognize intervals when LM_IN_PROGRESS, Laszlo Ersek, 2013/07/18
[Qemu-devel] [RFC 5/6] OptsVisitor: opts_type_uint64(): recognize intervals when LM_IN_PROGRESS, Laszlo Ersek, 2013/07/18
[Qemu-devel] [RFC 6/6] OptsVisitor: don't try to flatten overlong integer ranges, Laszlo Ersek, 2013/07/18