xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Study Xen <studyxen@gmail.com>
To: Tim Deegan <tim@xen.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: unable to capture an expected page fault
Date: Tue, 17 Jan 2012 13:11:37 -0500	[thread overview]
Message-ID: <CAJEOSFsECuhG1UDH+DCUO650URE=+nGv6=V236kNVUKNipMWmg@mail.gmail.com> (raw)
In-Reply-To: <20120117111222.GC74654@ocelot.phlegethon.org>


[-- Attachment #1.1: Type: text/plain, Size: 1476 bytes --]

Hello Tim,

Thanks for your reply. I am actually learning (and the same time trying to
port) the code written by a former student. That is why it is currently
hard for me to clearly explain what have been modified in the code.

The former member's intention was to make use of Xen's ability of modifying
pagetables underneath the guest kernel to achieve data protection of user
applications from a compromised kernel. So his modification scattered into
several places, mainly in Xen's memory management code and interrupt
handling code. Unfortunately I have not been able to pinpoint which code
caused the current bug I mentioned in the previous mail.

X


On Tue, Jan 17, 2012 at 6:12 AM, Tim Deegan <tim@xen.org> wrote:

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

[-- Attachment #1.2: Type: text/html, Size: 1990 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

      reply	other threads:[~2012-01-17 18:11 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
2012-01-17 18:11   ` Study Xen [this message]

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='CAJEOSFsECuhG1UDH+DCUO650URE=+nGv6=V236kNVUKNipMWmg@mail.gmail.com' \
    --to=studyxen@gmail.com \
    --cc=tim@xen.org \
    --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).