From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 07A49CF7A for ; Fri, 17 Mar 2017 14:52:10 +0100 (CET) Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C0B7CC1C5DE6; Fri, 17 Mar 2017 13:52:10 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com C0B7CC1C5DE6 Authentication-Results: ext-mx07.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx07.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=mst@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com C0B7CC1C5DE6 Received: from redhat.com (unknown [10.10.124.129]) by smtp.corp.redhat.com (Postfix) with SMTP id 6FD7B1796D; Fri, 17 Mar 2017 13:52:07 +0000 (UTC) Date: Fri, 17 Mar 2017 15:52:06 +0200 From: "Michael S. Tsirkin" To: Thomas Monjalon Cc: "Wiles, Keith" , Jason Wang , Vincent JARDIN , Stephen Hemminger , "O'Driscoll, Tim" , "Legacy, Allain (Wind River)" , "Yigit, Ferruh" , dev@dpdk.org, "Jolliffe, Ian (Wind River)" , Markus Armbruster , Stefan Hajnoczi Message-ID: <20170317155036-mutt-send-email-mst@kernel.org> References: <1488414008-162839-1-git-send-email-allain.legacy@windriver.com> <9242BBFE-279B-46E3-BC04-62F1FE897824@intel.com> <3140337.WIddM6FeqF@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3140337.WIddM6FeqF@xps13> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Fri, 17 Mar 2017 13:52:11 +0000 (UTC) Subject: Re: [dpdk-dev] [PATCH v4 00/17] Wind River Systems AVP PMD vs virtio? - ivshmem is back X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2017 13:52:11 -0000 On Fri, Mar 17, 2017 at 09:48:38AM +0100, Thomas Monjalon wrote: > I think there is one interesting technological point in this thread. > We are discussing about IVSHMEM but its support by Qemu is confused. > This feature is not in the MAINTAINERS file of Qemu. > Please Qemu maintainers, what is the future of IVSHMEM? You should try asking this question on the qemu mailing list. Looking at archives, Jan Kiszka was the last one who expressed some interest in this device. -- MST