Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756456AbZLXKHA (ORCPT ); Thu, 24 Dec 2009 05:07:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751430AbZLXKG7 (ORCPT ); Thu, 24 Dec 2009 05:06:59 -0500 Received: from mx1.redhat.com ([209.132.183.28]:18368 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751338AbZLXKG6 (ORCPT ); Thu, 24 Dec 2009 05:06:58 -0500 Date: Thu, 24 Dec 2009 12:01:59 +0200 From: "Michael S. Tsirkin" To: "Ira W. Snyder" Cc: Gregory Haskins , Kyle Moffett , Ingo Molnar , Avi Kivity , kvm@vger.kernel.org, Andrew Morton , torvalds@linux-foundation.org, "linux-kernel@vger.kernel.org" , netdev@vger.kernel.org, "alacrityvm-devel@lists.sourceforge.net" Subject: Re: [GIT PULL] AlacrityVM guest drivers for 2.6.33 Message-ID: <20091224100159.GA26152@redhat.com> References: <4B1D4F29.8020309@gmail.com> <20091218215107.GA14946@elte.hu> <4B2F9582.5000002@gmail.com> <20091222075742.GB26467@elte.hu> <4B3103B4.4070708@gmail.com> <4B3254B4.2080602@gmail.com> <20091223192808.GA30700@ovro.caltech.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091223192808.GA30700@ovro.caltech.edu> User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1550 Lines: 33 On Wed, Dec 23, 2009 at 11:28:08AM -0800, Ira W. Snyder wrote: > On Wed, Dec 23, 2009 at 12:34:44PM -0500, Gregory Haskins wrote: > > On 12/23/09 1:15 AM, Kyle Moffett wrote: > > > On Tue, Dec 22, 2009 at 12:36, Gregory Haskins > > > wrote: > > >> On 12/22/09 2:57 AM, Ingo Molnar wrote: > > >>> * Gregory Haskins wrote: > > >>>> Actually, these patches have nothing to do with the KVM folks. [...] > > >>> > > >>> That claim is curious to me - the AlacrityVM host > > >> > > >> It's quite simple, really. These drivers support accessing vbus, and > > >> vbus is hypervisor agnostic. In fact, vbus isn't necessarily even > > >> hypervisor related. It may be used anywhere where a Linux kernel is the > > >> "io backend", which includes hypervisors like AlacrityVM, but also > > >> userspace apps, and interconnected physical systems as well. So focus on interconnecting physical systems I think would be one way for vbus to stop conflicting with KVM. If drivers for such systems appear I expect that relevant (hypervisor-agnostic) vbus bits would be very uncontroversial. This would not be the first technology to make the jump from attempting to be a PCI replacement to being an interconnect btw, I think infiniband did this as well. -- MST -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/