From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wright Subject: Re: [RFC] Genapic in x86_64 Dom0 Date: Mon, 22 Aug 2005 11:57:55 -0700 Message-ID: <20050822185755.GY7762@shell0.pdx.osdl.net> References: <20050822182036.GV7762@shell0.pdx.osdl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Chris Wright , xen-devel@lists.xensource.com, "Puthiyaparambil, Aravindh" List-Id: xen-devel@lists.xenproject.org * Keir Fraser (Keir.Fraser@cl.cam.ac.uk) wrote: > I suspect we might be best off just diverging completely and having > our own file that implements enough of the local APIC "interface" to > get everything else to build, but is basically a set of no-ops. That's > basically what we have for arch/xen/i386. OK, that's more or less what I was thinkg (re: no-ops). > Maintaining processor and lapic info is pretty pointless since those > things aren't under domain 0's control, although it may be as easy to > do so as not. My intention was more about being able to run more code paths without having #if CONFIG_XEN if possible to hand to trivial or no-op stub instead.