>>> On 20.06.16 at 17:15, <andrey2...@gmail.com> wrote: Argh - I had started a second reply. This was actually meant to be part of it.
> On Mon, Jun 20, 2016 at 4:56 AM, Jan Beulich <jbeul...@suse.com> wrote: > >> >>> On 20.06.16 at 00:03, <andrey2...@gmail.com> wrote: >> > Follow up on >> http://www.gossamer-threads.com/lists/xen/devel/436000#436000 >> > Using >> http://eli.thegreenplace.net/2008/08/15/intersection-of-1d-segments as >> > reference. >> > >> > New value >> > |---------------| >> > >> > f1 f5 >> > |---| |-----| >> > f2 f4 >> > |-----| f3 |-----| >> > |-----| >> > >> > Given a new value of the type above, Current logic will not >> > allow applying parts of the new value overlapping with f3 filter. >> > only f2 and f4. >> >> I remains unclear what f1...f5 are meant to represent here. >> > > f1-f5 would be config_field[] such as header_common in conf_space_header.c > or any other config_field added (by adding quirks for example). Ah, but these are intended to not overlap. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
