All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: mukesh.rathor@oracle.com
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: 32bit PAE PV guest on 64bit hypervisor
Date: Tue, 14 Apr 2009 08:59:47 -0700	[thread overview]
Message-ID: <49E4B2F3.1050307@goop.org> (raw)
In-Reply-To: <49E40563.4010505@oracle.com>

Mukesh Rathor wrote:
> Hi,
>
> Been chasing down this message from guest boot:
>
> (XEN) mm.c:1841:d1 Error pfn 7f36a: rd=ffff8300cea28080,
> od=0000000000000000, caf=00000000, taf=0000000000000000
> (XEN) mm.c:730:d1 Error getting mfn 7f36a (pfn 5555555555555555) from L1
> entry 000000007f36a025 for dom1
> (XEN) mm.c:3700:d1 ptwr_emulate: fixing up invalid PAE PTE
> 000000007f36a025
>
> Firstly, on a >64GB system, looks like a 32bit guest can get mfn above 
> 64G.
>
> The above msg comes when the PV guest tries to do WP check. To that end,
> it does set_pte for mapping a (some swapper) temp page in test_wp_bit():
>
>       __set_fixmap(FIX_WP_TEST, __pa_symbol(&swapper_pg_dir), 
> PAGE_READONLY);
>       boot_cpu_data.wp_works_ok = do_test_wp_bit();
>       clear_fixmap(FIX_WP_TEST);
>
> ...
> /* use writable pagetables */
> static inline void set_pte(pte_t *ptep, pte_t pte)
> {
>         ptep->pte_high = pte.pte_high;
>     smp_wmb();
>     ptep->pte_low = pte.pte_low;
> }

What kernel version is this?

    J

  parent reply	other threads:[~2009-04-14 15:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14  3:39 32bit PAE PV guest on 64bit hypervisor Mukesh Rathor
2009-04-14  6:28 ` Keir Fraser
2009-04-23  1:57   ` Mukesh Rathor
2009-04-14 15:59 ` Jeremy Fitzhardinge [this message]
2009-04-14 18:06   ` Mukesh Rathor

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=49E4B2F3.1050307@goop.org \
    --to=jeremy@goop.org \
    --cc=mukesh.rathor@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.