From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v4 00/17] Wind River Systems AVP PMD vs
 virtio? - ivshmem is back
Date: Fri, 17 Mar 2017 15:52:06 +0200
Message-ID: <20170317155036-mutt-send-email-mst@kernel.org>
References: <1488414008-162839-1-git-send-email-allain.legacy@windriver.com>
 <bf5fc5b5-8939-c613-15f7-beabf1208c19@6wind.com>
 <9242BBFE-279B-46E3-BC04-62F1FE897824@intel.com>
 <3140337.WIddM6FeqF@xps13>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "Wiles, Keith" <keith.wiles@intel.com>, Jason Wang <jasowang@redhat.com>,
 Vincent JARDIN <vincent.jardin@6wind.com>,
 Stephen Hemminger <stephen@networkplumber.org>,
 "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
 "Legacy, Allain (Wind River)" <allain.legacy@windriver.com>,
 "Yigit, Ferruh" <ferruh.yigit@intel.com>, dev@dpdk.org,
 "Jolliffe, Ian (Wind River)" <ian.jolliffe@windriver.com>,
 Markus Armbruster <armbru@redhat.com>,
 Stefan Hajnoczi <stefanha@redhat.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by dpdk.org (Postfix) with ESMTP id 07A49CF7A
 for <dev@dpdk.org>; Fri, 17 Mar 2017 14:52:10 +0100 (CET)
Content-Disposition: inline
In-Reply-To: <3140337.WIddM6FeqF@xps13>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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