From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jiageng Yu <yujiageng734@gmail.com>
Subject: apic probe of 2.6.32.41 pv linux
Date: Fri, 27 May 2011 17:58:51 +0800
Message-ID: <BANLkTimUY4cLyZeff=N4tRU+1c3=KimTSw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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:

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!