linux-kernel - Re: hardwired VMI crap

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: <45F08FE4.5090909@vmware.com>
Date:	Thu, 08 Mar 2007 14:36:20 -0800
From:	Zachary Amsden <zach@...are.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Andi Kleen <ak@...e.de>, Jeremy Fitzhardinge <jeremy@...p.org>,
	tglx@...utronix.de, john stultz <johnstul@...ibm.com>,
	akpm@...ux-foundation.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Pratap Subrahmanyam <pratap@...are.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Daniel Hecht <dhecht@...are.com>,
	Daniel Arai <arai@...are.com>,
	Chris Wright <chrisw@...s-sol.org>
Subject: Re: hardwired VMI crap

Ingo Molnar wrote:
>   
>> [...] And apparently the VMI version is the same, just with some short 
>> cuts. Are you just worried about the ->apic_write() hooks or about 
>> something else too?
>>     
>
> i'm worried about those "shot cuts" (which in essence create software 
> variants of silicon), the hooks, the hardwirings combined with the 
> hypervisor-side ABIs creating a rigid mess that is harmful to Linux. 
> paravirt_ops and the hooks gives a license for all hypervisor 'backends' 
> to deviate into random arbitrary directions and to create all their 
> separate 'virtual silicon' playgrounds with no regard to Linux 
> maintainability. And once this gets released, Linux has no choice but to 
> play along.
>   

What?  And creating a high level API which allows you to implement 
totally random silicon with oodles of quirks and obfuscated 
implementation requirements creates more maintainability how?  We tried 
to stay as close as possible to the hardware ABI on purpose, 
specifically so we don't need to introduce 100 new concepts into the kernel.

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