Subject: Re: [PATCH] paravirt.h
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>, Andi Kleen <ak@muc.de>,
       Andrew Morton <akpm@osdl.org>,
       virtualization <virtualization@lists.osdl.org>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       Chris Wright <chrisw@sous-sol.org>
In-Reply-To: <44EB1BEB.60202@goop.org>
References: <1155202505.18420.5.camel@localhost.localdomain>
	 <44DB7596.6010503@goop.org>
	 <1156254965.27114.17.camel@localhost.localdomain> <44EB1BEB.60202@goop.org>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Tue, 22 Aug 2006 16:58:13 +0100
Message-Id: <1156262293.27114.24.camel@localhost.localdomain>
Mime-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 848
Lines: 19

Ar Maw, 2006-08-22 am 07:59 -0700, ysgrifennodd Jeremy Fitzhardinge:
> out, nothing is actually read-only in the kernel when using a 2M 
> mapping.  It's also ameliorated by the fact that some of the entrypoints 

Thats a loader problem. It ties directly in with things like relocatable
kernels. Arjan has been systematically working to get us "const" objects
and that needs to continue, and the more we can enforce it the more
security we get and the more bugs we catch.

It's also a mistake to assume the read-only doesn't help. Your 2MB
sections penalty isnt true in a virtualised environment.

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/