From: MaoXiaoyun <tinnycloud@hotmail.com>
To: jbeulich@novell.com
Cc: xen devel <xen-devel@lists.xensource.com>, keir.fraser@eu.citrix.com
Subject: RE: Xen-unstable panic: FATAL PAGE FAULT
Date: Wed, 1 Sep 2010 16:32:00 +0800 [thread overview]
Message-ID: <BAY121-W21C4906BE38FACAF71A8F3DA8B0@phx.gbl> (raw)
In-Reply-To: <4C7E257E02000078000139FB@vpn.id2.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 1124 bytes --]
Yes, you are right. I have it printted out, it is 18.
Thanks for correcting me.
I am interested in your assumption on list NULL check on last mail.
How can I set up a test to verify it?
> Date: Wed, 1 Sep 2010 09:05:50 +0100
> From: JBeulich@novell.com
> To: tinnycloud@hotmail.com
> CC: keir.fraser@eu.citrix.com; xen-devel@lists.xensource.com
> Subject: RE: [Xen-devel] Xen-unstable panic: FATAL PAGE FAULT
>
> >>> On 01.09.10 at 09:17, MaoXiaoyun <tinnycloud@hotmail.com> wrote:
>
> > As I go through the chunk merge code in free_heap_pages, one thing I'd like
> >
> > to mention is, previously, I printted out all domain pages when allocated,
> >
> > and I found the order in assgin_pages in
> > /xen-4.0.0/xen/common/page_alloc.c:1087,
> >
> > the order either be 0, or 9, and later I know that is because domain U
> > populate physmap
> >
> > 2M Bytes everytime.
> >
> >
> >
> > And here in the while statement, the order is compare with MAX_ORDER, which
> > is 20.
>
> Are you sure it's 20? MAX_ORDER should be 18 for x86 afaict.
>
> Jan
>
[-- Attachment #1.2: Type: text/html, Size: 1596 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-09-01 8:32 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SNT0-MC2-F12iKC1rdi000797d9@snt0-mc2-f12.Snt0.hotmail.com>
2010-08-26 4:49 ` Re:Re: Xen-unstable panic: FATAL PAGE FAULT MaoXiaoyun
2010-08-26 7:39 ` Keir Fraser
2010-08-26 8:59 ` MaoXiaoyun
2010-08-26 9:11 ` Keir Fraser
2010-08-30 8:47 ` MaoXiaoyun
2010-08-30 9:02 ` Keir Fraser
2010-08-30 13:03 ` MaoXiaoyun
2010-08-30 13:16 ` Keir Fraser
2010-08-31 13:49 ` MaoXiaoyun
2010-08-31 14:49 ` Keir Fraser
2010-08-31 15:00 ` Keir Fraser
2010-08-31 15:07 ` Jan Beulich
2010-08-31 16:01 ` Keir Fraser
2010-08-31 16:22 ` Jan Beulich
2010-08-31 16:35 ` Keir Fraser
2010-08-31 17:03 ` Keir Fraser
2010-09-01 7:17 ` MaoXiaoyun
2010-09-01 7:40 ` Keir Fraser
2010-09-01 8:05 ` Jan Beulich
2010-09-01 8:32 ` MaoXiaoyun [this message]
2010-09-01 8:02 ` Jan Beulich
2010-09-01 8:49 ` Keir Fraser
2010-09-01 9:01 ` Jan Beulich
2010-09-01 9:28 ` Keir Fraser
2010-09-01 9:48 ` MaoXiaoyun
2010-09-01 10:09 ` Jan Beulich
2010-09-01 9:06 ` MaoXiaoyun
2010-09-01 9:23 ` MaoXiaoyun
2010-09-01 9:58 ` Keir Fraser
2010-09-01 10:21 ` MaoXiaoyun
2010-09-01 10:25 ` Keir Fraser
2010-09-01 10:28 ` Keir Fraser
2010-09-01 10:34 ` Jan Beulich
2010-09-01 11:32 ` MaoXiaoyun
2010-09-01 7:54 ` Jan Beulich
2010-09-01 3:17 ` MaoXiaoyun
2010-02-06 22:56 Mark Hurenkamp
2010-02-07 11:56 ` Keir Fraser
2010-04-30 20:52 ` Bastian Blank
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=BAY121-W21C4906BE38FACAF71A8F3DA8B0@phx.gbl \
--to=tinnycloud@hotmail.com \
--cc=jbeulich@novell.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).