From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Re: APIC rework Date: Tue, 17 Nov 2009 03:45:15 +0000 Message-ID: References: <706158FABBBA044BAD4FE898A02E4BC201CD320368@pdsmsx503.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <706158FABBBA044BAD4FE898A02E4BC201CD320368@pdsmsx503.ccr.corp.intel.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: "Zhang, Xiantao" , Jeremy Fitzhardinge Cc: Xen-devel , "Han, Weidong" , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On 17/11/2009 03:13, "Zhang, Xiantao" wrote: >> Is there any way for the dom0 kernel to tell whether the hypervisor is >> implementing the new ABI, so it can choose how to set up interrupts. >> >> MAP_COMPAT_BIT doesn't seem like a very good name, because it implies >> that setting it reverts to "compatible" behaviour. I assume that >> leaving it clear enables the historical behaviour and setting it >> enables the new one (since old kernels won't be setting it). > > Maybe better change to MAP_NEW_ABI_BIT ? Since the hypervisor patch didn't > change old code path after introducing this bit, so it is very easy and safe > to backport to xen-3.4-testing tree, and make new dom0 be able to run top of > it. :) It's kind of a shame to need this though. Is there no way for the hypervisor to work out automatically whether an older dom0 is running? Or work out the trigger/level stuff for itself (after all it parses the relevant bios tables just like dom0)? -- Keir