From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55790) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z7RBl-0003NU-N8 for qemu-devel@nongnu.org; Tue, 23 Jun 2015 12:36:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z7RBh-0004XK-Gs for qemu-devel@nongnu.org; Tue, 23 Jun 2015 12:36:45 -0400 Received: from mx1.redhat.com ([209.132.183.28]:49025) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z7RBh-0004XE-C3 for qemu-devel@nongnu.org; Tue, 23 Jun 2015 12:36:41 -0400 Date: Tue, 23 Jun 2015 18:36:34 +0200 From: Thomas Huth Message-ID: <20150623183634.14c9d81e@thh440s> In-Reply-To: <1435058256-11838-1-git-send-email-cornelia.huck@de.ibm.com> References: <1435058256-11838-1-git-send-email-cornelia.huck@de.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 0/4] virtio-ccw: virtio-1 enablement List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Cornelia Huck Cc: qemu-devel@nongnu.org, mst@redhat.com On Tue, 23 Jun 2015 13:17:32 +0200 Cornelia Huck 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