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:37:26 +0300 Message-ID: <4E55DF96.3030309@kernel.org> 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> <1314249105.32391.64.camel@jaguar> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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 mail-ww0-f44.google.com ([74.125.82.44]:37197 "EHLO mail-ww0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751072Ab1HYFhb (ORCPT ); Thu, 25 Aug 2011 01:37:31 -0400 Received: by wwf5 with SMTP id 5so1969556wwf.1 for ; Wed, 24 Aug 2011 22:37:30 -0700 (PDT) In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 8/25/11 8:22 AM, Alexander Graf wrote: > > On 25.08.2011, at 00:11, Pekka Enberg wrote: > >> 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. > > Well, the nice thing is that you would get the guest side for free: > > http://gitorious.org/nahanni/guest-code/blobs/master/kernel_module/uio/uio_ivshmem.c > > You also didn't invent your own virtio protocol, no? :) No, because virtio drivers are in Linux kernel proper. Is ivshmem in the kernel tree or planned to be merged at some point? Pekka