WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] apic probe of 2.6.32.41 pv linux

To: Xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] apic probe of 2.6.32.41 pv linux
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
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=F03ArZei7VlZ7LrFSQGGXLN7LSY5YUg1V6uEKMDhQfA=; b=HuP894SYQQ8u6hTYKZOA5nl3BVw2NdY0fVn3xxcXNiR0ju7sit19DkRpuwEg6zSVeu VQ4c+IWXK8GHSRzrAvlAgG6MJA0OENrPpTC/lb7vTs8IzMwBvK4qyeJj6unU+UoZweRv OW7xNIoH0v4hLz7H2rg+wJXILEVXm7n8wWKfo=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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!

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>