linux-kernel - Re: [PATCH -v2] Add MCE support to KVM

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]

Date:	Tue, 21 Apr 2009 16:16:04 -0500
From:	Anthony Liguori <anthony@...emonkey.ws>
To:	Avi Kivity <avi@...hat.com>
CC:	Huang Ying <ying.huang@...el.com>, kvm@...r.kernel.org,
	linux-kernel@...r.kernel.org, Andi Kleen <andi@...stfloor.org>
Subject: Re: [PATCH -v2] Add MCE support to KVM

Avi Kivity wrote:
>
> Example: SMP.

There was no KVM support in QEMU at the time when SMP was introduced.  
Had there been, I see no reason not to do it in upstream QEMU.

> Example: vlan API.

You'll have to be more specific.  Do you mean the up coming vlan API 
refactoring?  That absolutely should be happening in upstream QEMU.

>>> For this kind of work, we can provide kvm-userspace.git as a kind of 
>>> playground where these experiments may be made.  kvm-userspace.git 
>>> exists to support kvm.git; while qemu.git has a life of its own and 
>>> more stringent barriers to acceptance.
>>
>> As long as people are using kvm-userspace.git instead of qemu.git, 
>> we're failing IMHO.  If kvm-userspace.git is basically the equivalent 
>> of the x86 git kernel tree, linux-next, or something like that, then 
>> that's a good thing.
>
> That's definitely a long term goal, but qemu is not yet at a point 
> where it is easy to implement new features efficiently.  Once it 
> reaches that state, kvm-userspace will become a simple staging ground 
> (or even disappear entirely).

The simple fact is that right now, Fedora ships kvm-userspace and calls 
it QEMU.  It builds packages for non-KVM enabled boards.  There is a 
very large userspace that consumes packages derived from kvm-userspace.  
Like it or not, kvm-userspace is not an experimental staging ground for 
QEMU.

The only reasonable things to do IMHO is for as much as humanly possible 
to be deferred to QEMU or for you to comes to terms with your role as a 
defacto QEMU maintainer and start pushing back more on patch sets that 
don't take into consideration TCG/non-KVM environments :-)

MCE is a perfect example of something that really has no reason to go in 
via kvm-userspace since we have enough KVM support in upstream QEMU.

Regards,

Anthony Liguori
--
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/