From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: apic probe of 2.6.32.41 pv linux Date: Fri, 27 May 2011 09:57:56 -0400 Message-ID: <20110527135756.GB6734@dumpdata.com> References: 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: Jiageng Yu Cc: Xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Fri, May 27, 2011 at 05:58:51PM +0800, Jiageng Yu wrote: > I have updated the pv linux kernel from 2.6.32.40 to 2.6.32.41. I > found the generic_apic_probe always led to a kernel panic when I try > to make the minimal DomU kernel. > > The 2.6.32.41 pv linux use the new apic probe mechanism: new..? What was it before? > > static __init int xen_safe_probe(void) { > if (!xen_initial_domain()) > return 0; > return 1; > } > > #ifdef CONFIG_XEN_DOM0 > #define xen_initial_domain() (xen_pv_domain() && xen_start_info->flags > & SIF_INITDOMAIN) > #else /* !CONFIG_XEN_DOM0 */ > #define xen_initial_domain() (0) > #endif /* CONFIG_XEN_DOM0 */ > > > If do not define the CONFIG_XEN_DOM0, xen_safe_probe will always > return 0 which causes the kernel panic. For the minimal DomU kernel, > the CONFIG_XEN_DOM0 is needless, and in this scenario, how to pass the > apic probe safely? > > Thanks! > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel