From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pekka Enberg Subject: Re: [PATCH] kvm tools: adds a PCI device that exports a host shared segment as a PCI BAR in the guest Date: Thu, 25 Aug 2011 08:11:45 +0300 Message-ID: <1314249105.32391.64.camel@jaguar> References: <20110824222510.GC14835@dancer.ca.sandia.gov> <232C9ABA-F703-4AE5-83BC-774C715D4D8F@suse.de> <20110825044913.GA24996@dancer.ca.sandia.gov> <1B781A18-BDBF-43EE-B4FE-C4393EC21AD3@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: David Evensky , David Evensky , Sasha Levin , kvm@vger.kernel.org, mingo@elte.hu To: Alexander Graf Return-path: Received: from filtteri6.pp.htv.fi ([213.243.153.189]:42041 "EHLO filtteri6.pp.htv.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751248Ab1HYFLu (ORCPT ); Thu, 25 Aug 2011 01:11:50 -0400 In-Reply-To: <1B781A18-BDBF-43EE-B4FE-C4393EC21AD3@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: On Wed, 2011-08-24 at 23:52 -0500, Alexander Graf wrote: > > Isn't ivshmem in QEMU? If so, then I don't think there isn't any > > competition. How do you feel that these are competing? > > Well, it means that you will inside the guest have two different > devices depending whether you're using QEMU or kvm-tool. I don't see > the point in exposing different devices to the guest just because of > NIH. Why should a guest care which device emulation framework you're > using? It's a pretty special-purpose device that requires user configuration so I don't consider QEMU compatibility to be mandatory. It'd be nice to have but not something to bend over backwards for. Pekka