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: <4B32290D.8090008@redhat.com>
Date:	Wed, 23 Dec 2009 16:28:29 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
CC:	Ingo Molnar <mingo@...e.hu>,
	Anthony Liguori <anthony@...emonkey.ws>,
	Andi Kleen <andi@...stfloor.org>,
	Gregory Haskins <gregory.haskins@...il.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 12/23/2009 04:08 PM, Bartlomiej Zolnierkiewicz wrote:
>
>> The device model is exposed to the guest.  If you change it, the guest
>> breaks.
>>      
> Huh?  Shouldn't non-vbus aware guests continue to work just fine?
>    

Sure.  But we aren't merging this code in order not to use it.  If we 
switch development focus to vbus, we have to ask everyone who's riding 
on virtio to switch.  Alternatively we maintain both models.

If vbus was the only way to get this kind of performance, I know what 
I'd choose.  But if it isn't, why inflict the change on users?

Consider a pxe-booting guest (or virtio-blk vs. a future veblk).  Is 
switching drivers in initrd something you want your users to do? [1]

One of the advantages of virtualization is stable hardware.  I don't 
want to let it go without a very good reason.

[1] I remember the move from /dev/hda to /dev/sda a few years ago, it 
isn't a good memory.

-- 
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ