On Fri, 8 Jan 2016 16:25:18 +0100
Laurent Vivier wrote:
>
>
> On 08/01/2016 15:19, Greg Kurz wrote:
> > On Thu, 7 Jan 2016 19:32:37 +0100
> > Laurent Vivier wrote:
> >>
> >
> > Sorry for the late answer to this one, I got diverted :)
> >
> >>
> >> On 07/01/2016 12:32, Greg Kurz wrote:
> >>>
On 08/01/2016 15:19, Greg Kurz wrote:
> On Thu, 7 Jan 2016 19:32:37 +0100
> Laurent Vivier wrote:
>>
>
> Sorry for the late answer to this one, I got diverted :)
>
>>
>> On 07/01/2016 12:32, Greg Kurz wrote:
>>> When running a fully emulated device in cross-endian conditions, including
>>> a v
On Thu, 7 Jan 2016 19:32:37 +0100
Laurent Vivier wrote:
>
Sorry for the late answer to this one, I got diverted :)
>
> On 07/01/2016 12:32, Greg Kurz wrote:
> > When running a fully emulated device in cross-endian conditions, including
> > a virtio 1.0 device offered to a big endian guest, we
On 07/01/2016 12:32, Greg Kurz wrote:
> When running a fully emulated device in cross-endian conditions, including
> a virtio 1.0 device offered to a big endian guest, we need to fix the vnet
> headers. This is currently handled by the virtio_net_hdr_swap() function
> in the core virtio-net code