linux-kernel - Re: [ANNOUNCE] Native Linux KVM tool

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: <20110408105952.5e7c2ffb@schlenkerla.am.freescale.net>
Date:	Fri, 8 Apr 2011 10:59:52 -0500
From:	Scott Wood <scottwood@...escale.com>
To:	Anthony Liguori <anthony@...emonkey.ws>
CC:	Ingo Molnar <mingo@...e.hu>, Avi Kivity <avi@...hat.com>,
	Pekka Enberg <penberg@...nel.org>,
	<linux-kernel@...r.kernel.org>, <aarcange@...hat.com>,
	<mtosatti@...hat.com>, <kvm@...r.kernel.org>, <joro@...tes.org>,
	<penberg@...helsinki.fi>, <asias.hejun@...il.com>,
	<gorcunov@...il.com>
Subject: Re: [ANNOUNCE] Native Linux KVM tool

On Thu, 7 Apr 2011 21:14:06 -0500
Anthony Liguori <anthony@...emonkey.ws> wrote:

> If someone was going to seriously go about doing something like this, a 
> better approach would be to start with QEMU and remove anything non-x86 
> and all of the UI/command line/management bits and start there.
> 
> There's nothing more I'd like to see than a viable alternative to QEMU 
> but ignoring any of the architectural mistakes in QEMU and repeating 
> them in a new project isn't going to get there.

Supporting only a single architecture sounds like a significant
architectural mistake...  only x86 deserves clean code?

-Scott

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