From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Evensky <evensky@dancer.ca.sandia.gov>
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 08:05:48 -0700
Message-ID: <20110826150548.GA758@dancer.ca.sandia.gov>
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>
 <CAJSP0QVB-7Bncx8K4udnC=BZq1994u44_8t0rddFDMQaHYLH7Q@mail.gmail.com>
 <CAOJsxLFDg+xZ0=eDC5NkAAPNf71nSXYQvYfe2jSRr9p=dE4wEQ@mail.gmail.com>
 <CAJSP0QW3SWDtq_CJzohQ+xz66OkD1ABsYM4scnp2YTmDVsONKg@mail.gmail.com>
 <1314271548.3692.22.camel@lappy>
 <20110825150806.GF24996@dancer.ca.sandia.gov>
 <1314340438.3647.30.camel@lappy>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	Pekka Enberg <penberg@kernel.org>,
	Alexander Graf <agraf@suse.de>, kvm@vger.kernel.org,
	cam@cs.ualberta.ca
To: Sasha Levin <levinsasha928@gmail.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from sentry-two.sandia.gov ([132.175.109.14]:56285 "EHLO
	sentry-two.sandia.gov" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753251Ab1HZPGA (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 26 Aug 2011 11:06:00 -0400
Content-Disposition: inline
In-Reply-To: <1314340438.3647.30.camel@lappy>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>


Sasha,
That is wonderful. It sounds like it should be OK, and will be happy
to test.

\dae

On Fri, Aug 26, 2011 at 09:33:58AM +0300, Sasha Levin wrote:
> 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.
> 
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html