From: "Jonathan M. McCune" <jonmccune@cmu.edu>
To: xen-devel@lists.xensource.com
Subject: page fault handling in Xen
Date: Sat, 08 Oct 2005 18:39:52 -0400 [thread overview]
Message-ID: <43484AB8.1010701@cmu.edu> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 883 bytes --]
Hello,
We're curious about page fault handling in Xen-devel. In particular,
during kernel boot-up, the kernel tests if the CPU "honours the WP bit".
This causes a page fault with error code 3 (expected behavior). Does
Xen still make a copy of the execution stack frame on the guest OS
stack, as specified in the original "Xen and the Art of Virtualization"
paper? There is a footnote here that suggests that using a pre-agreed
shared memory location might be a better option. Has this change been
implemented?
After the WP-test page fault is taken, what is supposed to happen from
Xen's perspective on the return from the page fault handler? In normal
linux, the exception handler changes its own return address (i.e.,
modifies the EIP register) to be the "fixup" address. Does this still
happen with XenoLinux, or does the hypervisor get involved?
Thanks,
-Jon
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3170 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 reply other threads:[~2005-10-08 22:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-08 22:39 Jonathan M. McCune [this message]
2005-10-08 22:34 ` page fault handling in Xen Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2007-03-02 9:09 jeet
2007-03-02 9:36 ` Tim Deegan
2007-03-02 12:06 jeet
2007-03-02 13:35 ` Tim Deegan
2007-03-05 6:29 jeet
2007-03-05 8:19 ` Keir Fraser
2007-03-05 13:09 jeet
2007-03-05 13:21 ` Tim Deegan
2007-03-06 13:16 jeet
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=43484AB8.1010701@cmu.edu \
--to=jonmccune@cmu.edu \
--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.