From mboxrd@z Thu Jan  1 00:00:00 1970
From: Olivier MATZ <olivier.matz@6wind.com>
Subject: Re: [Qemu-devel] Why I advise against using ivshmem
Date: Fri, 13 Jun 2014 11:48:11 +0200
Message-ID: <539AC8DB.4040109@6wind.com>
References: <20140610184818.2e490419@nbschild1> <53978375.6090707@6wind.com> <87ppie1v4r.fsf@blackfin.pond.sub.org> <20140612094413.15e56938@nbschild1> <87vbs6qjhj.fsf_-_@blackfin.pond.sub.org> <5399CF09.8030803@6wind.com> <87ppidnqmy.fsf@blackfin.pond.sub.org> <539AC3E0.9090404@6wind.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Henning Schild <henning.schild@siemens.com>,
	David Marchand <david.marchand@6wind.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	"thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>
To: Vincent JARDIN <vincent.jardin@6wind.com>,
	Markus Armbruster <armbru@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from zoll.droids-corp.org ([94.23.50.67]:38401 "EHLO
	mail.droids-corp.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752915AbaFMK1l (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 13 Jun 2014 06:27:41 -0400
In-Reply-To: <539AC3E0.9090404@6wind.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Hello,

On 06/13/2014 11:26 AM, Vincent JARDIN wrote:
> ivhsmem does not require hugetlbfs. It is optional.
>
>  > * it doesn't require ivshmem (it does require shared memory, which
>  > will also be added to 2.1)

Right, hugetlbfs is not required. A posix shared memory or tmpfs
can be used instead. For instance, to use /dev/shm/foobar:

   qemu-system-x86_64 -enable-kvm -cpu host [...] \
      -device ivshmem,size=16,shm=foobar


Regards,
Olivier