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]

Message-ID: <49EE304D.5060108@redhat.com>
Date:	Tue, 21 Apr 2009 23:45:01 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Anthony Liguori <anthony@...emonkey.ws>
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

Anthony Liguori wrote:
> Avi Kivity wrote:
>> No argument.  But some kernel features will require major rework in 
>> qemu before we can support them properly.  We'll still want to bring 
>> them to users quickly so users can enjoy them (and we can enjoy users 
>> testing them).  Waiting for a qemu rework may take a while, and we'll 
>> lose valuable feedback.
>
> Then we're failing.  If a particular implementation of a feature is 
> acceptable for kvm-userspace users, and we don't take it in QEMU 
> without requiring a huge amount of different work, then it suggests 
> something is broken about the QEMU process.
>

Example: SMP.
Example: vlan API.

>> 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).

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

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