xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jiageng Yu <yujiageng734@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Xen-devel@lists.xensource.com
Subject: Re: apic probe of 2.6.32.41 pv linux
Date: Fri, 27 May 2011 22:44:05 +0800	[thread overview]
Message-ID: <BANLkTinydmZz5z+oiJGdjMDOtAd87Ooh2w@mail.gmail.com> (raw)
In-Reply-To: <20110527135756.GB6734@dumpdata.com>

2011/5/27 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>:
> 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?


The linux kernel will invoke probe_default, which permanently returns 1.
I wander to know may I just return 1 in 2.6.32.41 kernel? If there is
no further problems.


>>
>> 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
>

  reply	other threads:[~2011-05-27 14:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-27  9:58 apic probe of 2.6.32.41 pv linux Jiageng Yu
2011-05-27 13:57 ` Konrad Rzeszutek Wilk
2011-05-27 14:44   ` Jiageng Yu [this message]
2011-05-27 15:22     ` Stefano Stabellini
2011-05-27 15:24     ` Konrad Rzeszutek Wilk
     [not found] <BANLkTiketgpSQMaEBnHhpDmbXVYT8Qg4JA@mail.gmail.com>
     [not found] ` <4DE01762.6020102@goop.org>
2011-05-28  4:56   ` Jiageng Yu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BANLkTinydmZz5z+oiJGdjMDOtAd87Ooh2w@mail.gmail.com \
    --to=yujiageng734@gmail.com \
    --cc=Xen-devel@lists.xensource.com \
    --cc=konrad.wilk@oracle.com \
    --cc=stefano.stabellini@eu.citrix.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).