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

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

Message-ID: <44D3C37F.7020803@linux.intel.com>
Date:	Fri, 04 Aug 2006 15:00:31 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	David Lang <dlang@...italinsight.com>
CC:	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, jeremy@...p.org
Subject: Re: A proposal - binary

David Lang wrote:
> On Fri, 4 Aug 2006, Arjan van de Ven wrote:
> 
>> David Lang wrote:
>>> I'm not commenting on any of the specifics of the interface calls (I 
>>> trust you guys to make that be sane :-) I'm just responding the the 
>>> idea that the interface actually needs to be locked down to an ABI as 
>>> opposed to just source-level compatability.
>>
>> you are right that the interface to the HV should be stable. But those 
>> are going
>> to be specific to the HV, the paravirt_ops allows the kernel to 
>> smoothly deal
>> with having different HV's.
>> So in a way it's an API interface to allow the kernel to deal with 
>> multiple
>> different ABIs that exist today and will in the future.
> 
> so if I understand this correctly we are saying that a kernel compiled 
> to run on hypervisor A would need to be recompiled to run on hypervisor 
> B, and recompiled again to run on hypervisor C, etc
> 
no the actual implementation of the operation structure is dynamic and can be picked
at runtime, so you can compile a kernel for A,B *and* C and at runtime the kernel
picks the one you have
-
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/