> -----Original Message-----
> From: Andrii Anisov [mailto:andrii.ani...@gmail.com]
> Sent: 16 February 2017 12:46
> To: Paul Durrant <paul.durr...@citrix.com>
> Cc: xen-de...@lists.xenproject.org; andrii_ani...@epam.com; Andrew
> Cooper <andrew.coop...@citrix.com>; George Dunlap
> <george.dun...@citrix.com>; Ian Jackson <ian.jack...@citrix.com>;
> jbeul...@suse.com; konrad.w...@oracle.com; sstabell...@kernel.org; Tim
> (Xen.org) <t...@xen.org>; Wei Liu <wei.l...@citrix.com>
> Subject: Re: [RFC 0/6] Rangeset generalisation
> Dear Paul,
> > The cleanup seems a good thing to do to me.
> So I would collect comments, rebase it to latest master and push the
> second version without RFC.
> > Any particular reason this series is RFC?
> The reason to make this series was an intention to use rangesets to
> manage mmio ranges in our shared coprocessor framework. It was planned
> to extend range with `void* priv` to extend functionality.
> Unfortunately the rangeset feature to merge ranges makes it unusable
> for our needs. Also linked list, even sorted, is not really good in
> Another concern was how community react on the change into generic code.
Many moons ago there were patches to use rbtree for rangesets. Perhaps it would
be worth reviving that idea?
> Andrii Anisov.
Xen-devel mailing list