[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] apic probe of pv linux

  • To: Xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Jiageng Yu <yujiageng734@xxxxxxxxx>
  • Date: Fri, 27 May 2011 17:58:51 +0800
  • Cc:
  • Delivery-date: Fri, 27 May 2011 05:56:30 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=lqM9Wd3Yzb1jZynz9WvDsQ8Y9FkXNn+xeuYAgr8cv5hg7YmMuw7iiNpsbQlcsfBUc4 hnUJnPumDLrxD9D03kuU9jJXlcxBtClvhDdjpWn9qYV5FfX3qpW91JcHQQEdp+zoom7o rtp0Xb9CtMAv4ddjf3f2an8rvvHDS8eCuU6es=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I have updated the pv linux kernel from to I
found the generic_apic_probe always led to a kernel panic when I try
to make the minimal DomU kernel.

The pv linux use the new apic probe mechanism:

static __init int xen_safe_probe(void) {
        if (!xen_initial_domain())
                return 0;
        return 1;

#define xen_initial_domain()    (xen_pv_domain() && xen_start_info->flags
#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?


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.