Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754166AbbBTKHc (ORCPT ); Fri, 20 Feb 2015 05:07:32 -0500 Received: from e06smtp13.uk.ibm.com ([195.75.94.109]:33101 "EHLO e06smtp13.uk.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753871AbbBTKHa (ORCPT ); Fri, 20 Feb 2015 05:07:30 -0500 Subject: [PATCH 0/3] vhost_net: support for cross endian guests From: Greg Kurz To: "Michael S. Tsirkin" Cc: Cedric Le Goater , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, virtualization@lists.linux-foundation.org Date: Fri, 20 Feb 2015 11:07:24 +0100 Message-ID: <20150220100724.18608.74654.stgit@bahia.local> User-Agent: StGit/0.17-dirty MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 15022010-0013-0000-0000-000003088164 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1197 Lines: 39 Hi, This patchset allows vhost_net to be used with legacy virtio when guest and host have a different endianness. It is based on previous work by Cédric Le Goater: https://www.mail-archive.com/kvm-ppc@vger.kernel.org/msg09848.html As suggested by MST: - the API now asks for a specific format (big endian) instead of the hint whether byteswap is needed or not (patch 1) - rebased on top of the virtio-1 accessors (patch 2) Patch 3 is a separate fix: I think it is also valid for virtio-1. Please comment. --- Greg Kurz (3): vhost: add VHOST_VRING_F_LEGACY_BIG_ENDIAN flag vhost: add support for legacy virtio vhost_net: fix virtio_net header endianness drivers/vhost/net.c | 32 ++++++++++++++++++++++++++------ drivers/vhost/vhost.c | 6 +++++- drivers/vhost/vhost.h | 23 +++++++++++++++++------ include/uapi/linux/vhost.h | 2 ++ 4 files changed, 50 insertions(+), 13 deletions(-) -- Greg -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/