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 14:15:22 +0300 Message-ID: References: <20110824222510.GC14835@dancer.ca.sandia.gov> <232C9ABA-F703-4AE5-83BC-774C715D4D8F@suse.de> <20110825044913.GA24996@dancer.ca.sandia.gov> <1314248794.32391.60.camel@jaguar> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: David Evensky , Alexander Graf , David Evensky , Sasha Levin , kvm@vger.kernel.org, Ingo Molnar To: Stefan Hajnoczi Return-path: Received: from mail-gw0-f46.google.com ([74.125.83.46]:64091 "EHLO mail-gw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752204Ab1HYLPX convert rfc822-to-8bit (ORCPT ); Thu, 25 Aug 2011 07:15:23 -0400 Received: by gwaa12 with SMTP id a12so1647695gwa.19 for ; Thu, 25 Aug 2011 04:15:23 -0700 (PDT) In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On Thu, Aug 25, 2011 at 1:59 PM, Stefan Hajnoczi w= rote: > Introducing yet another non-standard and non-Linux interface doesn't > help though. =A0If there is no significant improvement over ivshmem t= hen > it makes sense to let ivshmem gain critical mass and more users > instead of fragmenting the space. Look, I'm not going to require QEMU compatibility from tools/kvm contributors. If you guys really feel that strongly about the interface, then either - Get Rusty's "virtio spec pixie pee" for ivshmem - Get the Linux driver merged to linux-next - Help out David and Sasha to change interface But don't ask me to block clean code from inclusion to tools/kvm because it doesn't have a QEMU-capable interface. Pekka