linux-kernel - Re: [GIT PULL] Native Linux KVM tool for 3.1

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: <20110725114106.GA11393@infradead.org>
Date:	Mon, 25 Jul 2011 07:41:06 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Olivier Galibert <galibert@...ox.com>
Cc:	Christoph Hellwig <hch@...radead.org>, Ingo Molnar <mingo@...e.hu>,
	Alexander Graf <agraf@...e.de>,
	Pekka Enberg <penberg@...nel.org>,
	Jan Kiszka <jan.kiszka@....de>, torvalds@...ux-foundation.org,
	avi@...hat.com, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
	gorcunov@...il.com, levinsasha928@...il.com, asias.hejun@...il.com,
	prasadjoshi124@...il.com
Subject: Re: [GIT PULL] Native Linux KVM tool for 3.1

On Mon, Jul 25, 2011 at 01:34:25PM +0200, Olivier Galibert wrote:
> You need someone with taste in the loop.  But if you do, "evolved" is
> always better than "designed before you actually know what you need".
> 
> As I'm sure you perfectly know, for the matter.

Neither is actually helpful.  You reall want reference implementation
on both sides of an ABI, _and_ documentation.  And yes, usually you'll
need a few iterations over it.  In theory you can do that in a "tightly
integrated" enviroment as well, but practice shows simply boilds down
to commiting the bloody thing.

I'm also not sure why we even bother to focus with this side-line
discussion.  It's not like the kvm (as in the kernel kvm module)
developers have written the kvm tools.  It's just another userspace for
the kvm userspace (the fifth if I count correctly), and so far the
reference and often only implementation of any new kvm module feature
is for qemu-kvm.  So no matter where kvm tools lives, if you guys one
day actually start doing major kvm core features it will still evolve
discussing them with the main consumer of those interfaces.
--
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/