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]

Date:	Thu, 03 Aug 2006 16:40:53 -0700
From:	Zachary Amsden <zach@...are.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Greg KH <greg@...ah.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...l.org>,
	Andrew Morton <akpm@...l.org>,
	Christoph Hellwig <hch@...radead.org>,
	Rusty Russell <rusty@...tcorp.com.au>, Jack Lo <jlo@...are.com>
Subject: Re: A proposal - binary

Alan Cox wrote:
> Ar Iau, 2006-08-03 am 15:31 -0700, ysgrifennodd Zachary Amsden:
>   
>> Alan Cox wrote:
>>     
>>> Could have fooled me. It seems to work for the IBM Mainframe people
>>> really well. 
>>>       
>> Yes, but not because of source compatibility.  It works because the 
>> hypervisor layer is actually architected in the hardware.
>>     
>
> The hardware has nothing to do with it. It works because the hypervisor
> API has a spec and is maintained compatibly. Its not entirely hardware
> architected either, it has chunks of interfaces that are not present
> hardware level or not meaningful at that level - the paging assists for
> example are purely a hypervisor interface as are hipersockets.
>   

Yes, it's part hardware, part software, a pseudo firmwarish mesh of the 
two.  When you've got multiple vendors involved, you need to paint the 
interface with a broader stroke so that the individual details of each 
don't get so involved, and you can do that in many different ways.  You 
still need an ABI, not just an API, though, for future compatibility of 
existing kernels, which is important to mainframe customers for 
migration as well as virtual machine users.

But I think we're running off into the weeds picking nits here..

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