On Wed, Dec 14, 2016 at 04:43:11PM +0100, Michal Suchánek wrote:
> On Wed, 14 Dec 2016 15:32:11 +0100
> Christophe Fergeau wrote:
>
> > Hey,
> >
> > On Mon, Nov 28, 2016 at 03:08:34PM +0100, Michal Suchanek wrote:
> > > This allows running big endian and little endian guest side by side
> > > us
On Wed, 14 Dec 2016 15:32:11 +0100
Christophe Fergeau wrote:
> Hey,
>
> On Mon, Nov 28, 2016 at 03:08:34PM +0100, Michal Suchanek wrote:
> > This allows running big endian and little endian guest side by side
> > using cut&paste between them.
> >
> > There is some general design idea that swapp
Hey,
On Mon, Nov 28, 2016 at 03:08:34PM +0100, Michal Suchanek wrote:
> This allows running big endian and little endian guest side by side using
> cut&paste between them.
>
> There is some general design idea that swapping should come as cloce to
> virtio_read/virtio_write as possible. In partic
Hi,
On Mon, Nov 28, 2016 at 03:08:34PM +0100, Michal Suchanek wrote:
> This allows running big endian and little endian guest side by side using
> cut&paste between them.
>
> There is some general design idea that swapping should come as cloce to
> virtio_read/virtio_write as possible. In particul
Hello,
On Mon, 28 Nov 2016 15:08:34 +0100
Michal Suchanek wrote:
> This allows running big endian and little endian guest side by side
> using cut&paste between them.
>
> There is some general design idea that swapping should come as cloce
> to virtio_read/virtio_write as possible. In particular
This allows running big endian and little endian guest side by side using
cut&paste between them.
There is some general design idea that swapping should come as cloce to
virtio_read/virtio_write as possible. In particular, the protocol between
vdagent and vdagentd is guest-specific and in native e
