Re: [GIT PULL] AlacrityVM guest drivers for 2.6.33

[Avi Kivity <avi@redhat.com>]

On 12/24/2009 11:31 AM, Gregory Haskins wrote:
> On 12/23/09 3:36 PM, Avi Kivity wrote:
>    
>> On 12/23/2009 06:44 PM, Gregory Haskins wrote:
>>      
>>>        
>>>>    - Are a pure software concept
>>>>
>>>>          
>>> By design.  In fact, I would describe it as "software to software
>>> optimized" as opposed to trying to shoehorn into something that was
>>> designed as a software-to-hardware interface (and therefore has
>>> assumptions about the constraints in that environment that are not
>>> applicable in software-only).
>>>
>>>
>>>        
>> And that's the biggest mistake you can make.
>>      
> Sorry, that is just wrong or you wouldn't have virtio either.
>    

Things are not black and white.  I prefer not to have paravirtualization 
at all.  When there is no alternative, I prefer to limit it to the 
device level and keep it off the bus level.

>>   Look at Xen, for
>> instance.  The paravirtualized the fork out of everything that moved in
>> order to get x86 virt going.  And where are they now? x86_64 syscalls
>> are slow since they have to trap to the hypervisor and (partially) flush
>> the tlb.  With npt or ept capable hosts performance is better for many
>> workloads on fullvirt.  And paravirt doesn't support Windows.  Their
>> unsung hero Jeremy is still trying to upstream dom0 Xen support.  And
>> they get to support it forever.
>>      
> We are only talking about PV-IO here, so not apples to apples to what
> Xen is going through.
>    

The same principles apply.

>> VMware stuck with the hardware defined interfaces.  Sure they had to
>> implement binary translation to get there, but as a result, they only
>> have to support one interface, all guests support it, and they can drop
>> it on newer hosts where it doesn't give them anything.
>>      
> Again, you are confusing PV-IO.  Not relevant here.   Afaict, vmware,
> kvm, xen, etc, all still do PV-IO and likely will for the foreseeable
> future.
>    

They're all doing it very differently:

- pure emulation (qemu e1000, etc.)
- pci device (vmware, virtio/pci)
- paravirt bus bridged through a pci device (Xen hvm, Hyper-V (I think), 
venet/vbus)
- paravirt bus (Xen pv, early vbus, virtio/lguest, virtio/s390)

The higher you are up this scale the easier things are, so once you get 
reasonable performance there is no need to descend further.

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