linux-kernel - Re: [PATCH 0/7] KVM: Kernel-based Virtual Machine

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: <4537D1FA.9090502@us.ibm.com>
Date:	Thu, 19 Oct 2006 14:28:58 -0500
From:	Anthony Liguori <aliguori@...ibm.com>
To:	Avi Kivity <avi@...ranet.com>
CC:	Andi Kleen <ak@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/7] KVM: Kernel-based Virtual Machine

Avi Kivity wrote:
> Anthony Liguori wrote:
>>>
>>> I have to go through the motions of creating a sourceforge project 
>>> for this and uploading it.  And yes, it is free.
>>
>> Don't even bother creating a project.  Just submit the patches back 
>> to QEMU.  There's been a lot of discussion about this functionality 
>> within QEMU.  There's no reason to fork QEMU yet again (Xen has given 
>> up and is now maintaining a patch queue).  In this case, there's no 
>> reason why you would even need a patch queue.
>
> We don't plan to fork qemu, too much good stuff is being added there.  
> However I want to submit the patch for inclusion only after (if?) the 
> driver is merged into the mainline kernel.  The patch is also not very 
> pretty at the moment.

I would recommend the opposite approach.  Something can go in QEMU more 
quickly than in the kernel and you'll get people actually testing it.  
If it gets in the kernel and there's no major userspace presence you 
won't have nearly the same amount of testers...

Regards,

Anthony Liguori

> I'll post it as a patch and probably a binary rpm for the lazy.
>
>

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