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 23:00:11 +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:
>>>
>>> So Avi, regardless of what interface is chosen for KVM, can you hold 
>>> off applying these patches until there is a TCG implementation?  
>>> Otherwise, we'll be playing catchup between kvm-userspace and 
>>> upstream QEMU forever.
>>
>> I have a feeling we will anyway,
>
> Not if we avoid committing things to kvm-userspace that would require 
> major reworking to get into upstream QEMU.  Fixing these issues is 
> much easier up front then down the road.
>

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.

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.

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