Re: [Xen-devel] [PATCH 3/3] tools/cpu-policy: Add unit tests and a fuzzing harness

2019-02-25 Thread Jan Beulich
>>> On 25.02.19 at 12:56, wrote: > On 07/01/2019 11:19, Jan Beulich wrote: > On 04.01.19 at 16:33, wrote: >>> The AFL harness currently notices that there are cases where we optimse the >>> serialised stream by omitting data beyond the various maximum leaves. >>> >>> Both sets of tests will b

Re: [Xen-devel] [PATCH 3/3] tools/cpu-policy: Add unit tests and a fuzzing harness

2019-02-25 Thread Andrew Cooper
On 07/01/2019 11:19, Jan Beulich wrote: On 04.01.19 at 16:33, wrote: >> The AFL harness currently notices that there are cases where we optimse the >> serialised stream by omitting data beyond the various maximum leaves. >> >> Both sets of tests will be extended with further libx86 work. >> >

Re: [Xen-devel] [PATCH 3/3] tools/cpu-policy: Add unit tests and a fuzzing harness

2019-01-07 Thread Jan Beulich
>>> On 04.01.19 at 16:33, wrote: > The AFL harness currently notices that there are cases where we optimse the > serialised stream by omitting data beyond the various maximum leaves. > > Both sets of tests will be extended with further libx86 work. > > Fix the sorting of the CPUID_GUEST_NR_* con

[Xen-devel] [PATCH 3/3] tools/cpu-policy: Add unit tests and a fuzzing harness

2019-01-04 Thread Andrew Cooper
The AFL harness currently notices that there are cases where we optimse the serialised stream by omitting data beyond the various maximum leaves. Both sets of tests will be extended with further libx86 work. Fix the sorting of the CPUID_GUEST_NR_* constants, noticed while writing the unit tests.