From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sasha Levin Subject: Re: [PATCH] kvm tools: adds a PCI device that exports a host shared segment as a PCI BAR in the guest Date: Fri, 26 Aug 2011 09:33:58 +0300 Message-ID: <1314340438.3647.30.camel@lappy> 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> <1314271548.3692.22.camel@lappy> <20110825150806.GF24996@dancer.ca.sandia.gov> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Stefan Hajnoczi , Pekka Enberg , Alexander Graf , kvm@vger.kernel.org, cam@cs.ualberta.ca To: David Evensky Return-path: Received: from mail-ww0-f44.google.com ([74.125.82.44]:50724 "EHLO mail-ww0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751244Ab1HZGeE (ORCPT ); Fri, 26 Aug 2011 02:34:04 -0400 Received: by wwf5 with SMTP id 5so3142314wwf.1 for ; Thu, 25 Aug 2011 23:34:03 -0700 (PDT) In-Reply-To: <20110825150806.GF24996@dancer.ca.sandia.gov> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, 2011-08-25 at 08:08 -0700, David Evensky wrote: > Adding in the rest of what ivshmem does shouldn't affect our use, *I > think*. I hadn't intended this to do everything that ivshmem does, > but I can see how that would be useful. It would be cool if it could > grow into that. David, I've added most of ivshmem on top of your driver (still working on fully understanding the client-server protocol). The changes that might affect your use have been simple: * The shared memory BAR is now 2 instead of 0. * Vendor and device IDs changed. * The device now has MSI-X capability in the header and supporting code to run it. If these points won't affect your use I think there shouldn't be any other issues. -- Sasha.