On Tue, Sep 15, 2009 at 05:39:27PM -0400, Gregory Haskins wrote: > Michael S. Tsirkin wrote: > > On Tue, Sep 15, 2009 at 04:43:58PM -0400, Gregory Haskins wrote: > >> Michael S. Tsirkin wrote: > >>> On Tue, Sep 15, 2009 at 04:08:23PM -0400, Gregory Haskins wrote: > >>>> No, what I mean is how do you surface multiple ethernet and consoles to > >>>> the guests? For Ira's case, I think he needs at minimum at least one of > >>>> each, and he mentioned possibly having two unique ethernets at one point. > >>>> > >>>> His slave boards surface themselves as PCI devices to the x86 > >>>> host. So how do you use that to make multiple vhost-based devices (say > >>>> two virtio-nets, and a virtio-console) communicate across the transport? > >>>> > >>>> There are multiple ways to do this, but what I am saying is that > >>>> whatever is conceived will start to look eerily like a vbus-connector, > >>>> since this is one of its primary purposes ;) > >>> Can't all this be in userspace? > >> Can you outline your proposal? > >> > >> -Greg > >> > > > > Userspace in x86 maps a PCI region, uses it for communication with ppc? > > > > And what do you propose this communication to look like? Who cares? Implement vbus protocol there if you like. > -Greg > -- 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
