From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:56821)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1Z7VIo-0006Iy-1I
	for qemu-devel@nongnu.org; Tue, 23 Jun 2015 17:00:18 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1Z7VIi-0007rO-Cp
	for qemu-devel@nongnu.org; Tue, 23 Jun 2015 17:00:17 -0400
Received: from mx1.redhat.com ([209.132.183.28]:48049)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1Z7VIi-0007rG-7N
	for qemu-devel@nongnu.org; Tue, 23 Jun 2015 17:00:12 -0400
Date: Tue, 23 Jun 2015 23:00:09 +0200
From: "Michael S. Tsirkin" <mst@redhat.com>
Message-ID: <20150623225929-mutt-send-email-mst@redhat.com>
References: <1435058256-11838-1-git-send-email-cornelia.huck@de.ibm.com>
	<20150623183634.14c9d81e@thh440s>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150623183634.14c9d81e@thh440s>
Subject: Re: [Qemu-devel] [PATCH 0/4] virtio-ccw: virtio-1 enablement
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Thomas Huth <thuth@redhat.com>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>, qemu-devel@nongnu.org

On Tue, Jun 23, 2015 at 06:36:34PM +0200, Thomas Huth wrote:
> On Tue, 23 Jun 2015 13:17:32 +0200
> Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
> 
> > Michael,
> > 
> > here's the virtio-ccw patches that Gerd had dropped due to conflicts
> > during his virtio-1 rebase. Patch 2 has been updated with my changes
> > to ensure big endian accesses (which was a separate patch before).
> > 
> > There might be more patches that were in my tree but are not yet upstream,
> > but I'm still digging myself out from under the post-vacation email pile.
> > 
> > I think these can still go into 2.4.
> 
> Is it safe enough to enable them by default already? If I've got
> the virtio-pci code right (see the patch description at
> https://lists.gnu.org/archive/html/qemu-devel/2015-06/msg01362.html),
> it is still disabled there by default - and "modern will be turned on by
> default once all remaining spec compilance issues are addressed".
> 
>  Thomas

I know of some compliance issues. It does work with current linux
guests.

-- 
MST