linux-kernel - Re: Xen & VMI?

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070306171813.GA21218@elte.hu>
Date:	Tue, 6 Mar 2007 18:18:13 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Zachary Amsden <zach@...are.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	virtualization <virtualization@...ts.osdl.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Roland McGrath <roland@...hat.com>, Andi Kleen <ak@...e.de>,
	linux-kernel@...r.kernel.org, Jan Beulich <jbeulich@...ell.com>
Subject: Re: Xen & VMI?


* Jeremy Fitzhardinge <jeremy@...p.org> wrote:

> > My suggestion would be for Linux to make only a /single/ external 
> > ABI promise: VMI. (and we can extend it with higher-level paravirt 
> > ops, etc.)
> 
> "VMI" is not a promise, it's just three letters.  It doesn't even mean 
> the same thing now as it did 12 months ago.  Turning "VMI" from three 
> letters into anything remotely like a promise is a huge amount of work 
> which requires:
> 
>    1. someone actually sit down and fully document what all those
>       entrypoints are going to do
>    2. everyone to implement them
>    3. someone to test that all the implementations conform to the
>       document (bearing in mind that if anyone is going to go to all
>       this effort, they're going to use this with non-Linux guests)
>    4. and repeat all that every subsequent update

There's no process needed. The only thing needed is to treat the Linux 
implementation as the reference design, documentation and specification. 
Treat it as we treat the Linux system calls. We promise not to change 
them. There's no "process" for that either, other than our promise, our 
taste and our best efforts - plus the backing of all distributions and 
the threat of a few million users who start yelling (or worse) if we 
break it ;)

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