From: Ingo Molnar Subject: Re: [patch 06/26] Xen-paravirt_ops: paravirt_ops: allocate a fixmap slot Date: Fri, 16 Mar 2007 10:31:45 +0100 Message-ID: <20070316093145.GR23174@elte.hu> References: <20070301232443.195603797@goop.org> <20070301232526.730138638@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20070301232526.730138638@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: Zachary Amsden , xen-devel@lists.xensource.com, virtualization@lists.osdl.org, Rusty Russell , linux-kernel@vger.kernel.org, Chris Wright , Andi Kleen , Andrew Morton List-Id: virtualization@lists.linuxfoundation.org * Jeremy Fitzhardinge wrote: > Allocate a fixmap slot for use by a paravirt_ops implementation. This > is intended for early-boot bootstrap mappings. Once the zones and > allocator have been set up, it would be better to use get_vm_area() to > allocate some virtual space. > > Xen uses this to map the hypervisor's shared info page, which doesn't > have a pseudo-physical page number, and therefore can't be mapped > ordinarily. It is needed early because it contains the vcpu state, > including the interrupt mask. Acked-by: Ingo Molnar Ingo