lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091224100159.GA26152@redhat.com>
Date:	Thu, 24 Dec 2009 12:01:59 +0200
From:	"Michael S. Tsirkin" <mst@...hat.com>
To:	"Ira W. Snyder" <iws@...o.caltech.edu>
Cc:	Gregory Haskins <gregory.haskins@...il.com>,
	Kyle Moffett <kyle@...fetthome.net>,
	Ingo Molnar <mingo@...e.hu>, Avi Kivity <avi@...hat.com>,
	kvm@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>,
	torvalds@...ux-foundation.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	netdev@...r.kernel.org,
	"alacrityvm-devel@...ts.sourceforge.net" 
	<alacrityvm-devel@...ts.sourceforge.net>
Subject: Re: [GIT PULL] AlacrityVM guest drivers for 2.6.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
> > > <gregory.haskins@...il.com> wrote:
> > >> On 12/22/09 2:57 AM, Ingo Molnar wrote:
> > >>> * Gregory Haskins <gregory.haskins@...il.com> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ