linux-kernel - Re: A proposal

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]

Date:	Fri, 04 Aug 2006 14:26:20 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	David Lang <dlang@...italinsight.com>
CC:	Arjan van de Ven <arjan@...ux.intel.com>,
	Antonio Vargas <windenntw@...il.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Andrew Morton <akpm@...l.org>, jeremy@...source.com,
	greg@...ah.com, zach@...are.com, linux-kernel@...r.kernel.org,
	torvalds@...l.org, hch@...radead.org, jlo@...are.com,
	xen-devel@...ts.xensource.com, simon@...source.com,
	ian.pratt@...source.com
Subject: Re: A proposal - binary

David Lang wrote:
> how can I compile in support for Xen4 on my 2.6.18 kernel? after all 
> xen 2 and xen3 are incompatable hypervisors so why wouldn't xen4 (and 
> I realize there is no xen4 yet, but there is likly to be one during 
> the time virtual servers created with 2.6.18 are still running)

Firstly, backwards compatibility is very important; I would guess that 
if there were a Xen4 ABI, the hypervisor would still support Xen3 for 
some time.  Secondly, if someone goes to the effort of backporting a 
Xen4 paravirtops driver for 2.6.18, then you could compile it in.

> I also am missing something here. how can a system be compiled to do 
> several different things for the same privilaged opcode (including 
> running that opcode) without turning that area of code into a 
> performance pig as it checks for each possible hypervisor being present?

Conceptually, the paravirtops structure is a structure of pointers to 
functions which get filled in at runtime to support whatever hypervisor 
we're running over.  But it also has the means to patch inline versions 
of the appropriate code sequences for performance-critical operations.

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