From: Tim Deegan <tim@xen.org>
To: Study Xen <studyxen@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: unable to capture an expected page fault
Date: Tue, 17 Jan 2012 11:12:22 +0000 [thread overview]
Message-ID: <20120117111222.GC74654@ocelot.phlegethon.org> (raw)
In-Reply-To: <CAJEOSFtHjhU1=eQ8ghDTcKvErso46OgAqOL8-jKeae0QnywDjw@mail.gmail.com>
Hi,
At 03:08 -0500 on 17 Jan (1326769684), Study Xen wrote:
> I was trying to modify part of Xen and faced a page fault missing issue.
>
> I am testing a PV Linux 64-bit guest (kernel 3.1.1, as dom0, the only
> domain in my setting) atop Xen 4.1.2. In an unmodified Xen, the Linux
> kernel's "native_set_pte" in "arch/x86/include/asm/pgtable_64.h" traps into
> Xen due to Xen's write-protection of the pagetable page. But in our
> modified version, this expected page fault seems missing.
Well, I suppose it must be something you changed. :) But since you don't
say what you changed I'm not sure how much we can help you. If the
pagetables are indeed correct then maybe you're missing a TLB flush
somewhere?
Tim.
next prev parent reply other threads:[~2012-01-17 11:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 8:08 unable to capture an expected page fault Study Xen
2012-01-17 11:12 ` Tim Deegan [this message]
2012-01-17 18:11 ` Study Xen
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=20120117111222.GC74654@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=studyxen@gmail.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.