From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: CONFIG_XEN_COMPAT_030002 broken? Date: Tue, 14 Nov 2006 11:50:45 +0000 Message-ID: References: <4559B322.76E4.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4559B322.76E4.0078.0@novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich , Gerd Hoffmann , Keir Fraser Cc: Xen devel list List-Id: xen-devel@lists.xenproject.org On 14/11/06 11:14, "Jan Beulich" wrote: >> By the way, the test of whether to poke in PAGE_USER can be done by looking >> at one of the initial mappings provided by the domain builder. If one of >> those ptes contains PAGE_USER, you know you need to use PAGE_USER for all >> kernel mappings. > > How would this work? adjust_guest_l1e() (and BASE_PROT for dom0) forces > PAGE_USER on even on 3.0.3, so I still shouldn't find any L1 page table > entries > not having this bit set when looking at them from kernel code. Oh, good point! Okay then the more straightforward XENVER_version check will have to be used: 3.0.3 and newer, versus 3.0.2 and older. -- Keir