linux-kernel - Re: [PATCH v3 00/41] linux: towards virtio-1 guest support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20141125100540.3b747d12.cornelia.huck@de.ibm.com>
Date:	Tue, 25 Nov 2014 10:05:40 +0100
From:	Cornelia Huck <cornelia.huck@...ibm.com>
To:	"Michael S. Tsirkin" <mst@...hat.com>
Cc:	linux-kernel@...r.kernel.org, David Miller <davem@...emloft.net>,
	rusty@....ibm.com, nab@...ux-iscsi.org, pbonzini@...hat.com
Subject: Re: [PATCH v3 00/41] linux: towards virtio-1 guest support

On Mon, 24 Nov 2014 21:12:05 +0200
"Michael S. Tsirkin" <mst@...hat.com> wrote:

> On Mon, Nov 24, 2014 at 07:48:31PM +0100, Cornelia Huck wrote:

> > vring_transport_features() seems to knock off the version 1 bit (I
> > wonder why I did not see that before, maybe VIRTIO_TRANSPORT_F_END had
> > not been increased before?). If I add VIRTIO_F_VERSION_1 in this
> > function, virtio-net and virtio-blk seem to work fine with version 1 on
> > virtio-ccw (tested with my old virtio-1 qemu branch).
> 
> What if we just move VIRTIO_TRANSPORT_F_END back for now?
> Does patch below fix it for you?

It does.

> 
> > I'll try to do a bit of reviewing tomorrow.
> 
> BTW could you post your latest qemu bits please?

I haven't done much work on virtio-1 lately, but I could rebase my
existing branch to current qemu.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/