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]

Message-ID: <44D244B9.907@vmware.com>
Date:	Thu, 03 Aug 2006 11:47:21 -0700
From:	Zachary Amsden <zach@...are.com>
To:	Antonio Vargas <windenntw@...il.com>
Cc:	Arjan van de Ven <arjan@...radead.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...l.org>, greg@...ah.com,
	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

Antonio Vargas wrote:
> I've been fishing in my mail archive and was unable to get any
> discussion about abstract mmu... do you know where I can get more info
> on that?

Here's one useful link:

http://lwn.net/Articles/124961/

>> - but there can be no progress until there is some kind of consensus on
>> what those are, and having an interface in the kernel is a requirement
>> for any deeper level of paravirtualization.
>>
>> Zach
>
> Here I'd like to say that I mentioned both mol and the sun T1 because
> so far we haven't had any discussion on whether any of their
> interfaces are worth copying for the x86 case. Also worth looking at
> would be the work done by IBM for ppc64 and s390, especially the last
> one is prone to be very optimised since their hypervisor work has been
> proven to work for a very long time.
>
> I sure don't mean to diss out both vmware and xen work on the field,
> given the rocky nature of the x86 architecture, but maybe taking a
> look at preexisting work can be a good idea if it hasn't been done
> earlier

Almost nothing from any other architecture makes sense for x86.  X86 is 
not a virtualizable architecture.  It has both classical problems - 
sensitive instructions, and also non-reversible CPU state.  Hardware 
virtualization is now making that easier, but simplifying the OS to 
avoid these problems is actually simpler and more efficient.  PPC64 and 
S390 had the benefit of being designed with virtualization in mind, and 
they still have "paravirtualized" kernel architectures when you look at 
the lower layers.

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/