xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: MaoXiaoyun <tinnycloud@hotmail.com>,
	xen devel <xen-devel@lists.xensource.com>
Cc: Jan Beulich <JBeulich@novell.com>
Subject: Re: Xen-unstable panic: FATAL PAGE FAULT
Date: Tue, 31 Aug 2010 16:00:35 +0100	[thread overview]
Message-ID: <C8A2D7A3.218DA%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <C8A2D509.218B6%keir.fraser@eu.citrix.com>

On 31/08/2010 15:49, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:

> I'm cc'ing Jan to see what we can get away with in doing arithmetic on
> page_info pointers. What's the guaranteed smallest aligned contiguous ranges
> of mfn in the frame_table now, Jan? (i.e., ranges in which adjacent
> page_info structs relate to adjacent MFNs)
> 
> If this is the problem I'm pretty sure we can come up with a patch quite
> easily, but depending on the answer to my above question to Jan, we may need
> to do some code auditing.

Actually I think we get away with it if it is guaranteed that:
pfn_pdx_bottom_mask >= (1<<MAX_ORDER)-1

I don't see that this is guaranteed by pfn_pdx_hole_setup() but it would be
easy to do, have no real harm on the technique's space saving, and I think
then all of our existing page_info pointer arithmetic would be guaranteed to
just work as it always has done.

Anyway, need to know if you have the line about "PFN compression" in your
'xm dmesg' boot output.

 -- Keir

  reply	other threads:[~2010-08-31 15:00 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 [this message]
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
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=C8A2D7A3.218DA%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=JBeulich@novell.com \
    --cc=tinnycloud@hotmail.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).