On Tue, Jan 19, 2016 at 8:11 AM, Peter Maydell wrote:
> On 18 January 2016 at 07:12, Peter Crosthwaite
> wrote:
>> From: Peter Crosthwaite
>>
>> There is a CPU data endianness test that is used to drive the
>> virtio_big_endian test.
>>
>> Move this up to the header so it can be more generally u
On 18 January 2016 at 07:12, Peter Crosthwaite
wrote:
> From: Peter Crosthwaite
>
> There is a CPU data endianness test that is used to drive the
> virtio_big_endian test.
>
> Move this up to the header so it can be more generally used for endian
> tests. The KVM specific cpu_syncronize_state cal
On Sun, Jan 17, 2016 at 11:12 PM, Peter Crosthwaite
wrote:
> From: Peter Crosthwaite
>
> There is a CPU data endianness test that is used to drive the
> virtio_big_endian test.
>
> Move this up to the header so it can be more generally used for endian
> tests. The KVM specific cpu_syncronize_stat
From: Peter Crosthwaite
There is a CPU data endianness test that is used to drive the
virtio_big_endian test.
Move this up to the header so it can be more generally used for endian
tests. The KVM specific cpu_syncronize_state call is left behind in the
virtio specific function.
Signed-off-by: P
