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@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
