From: Jacob Gorm Hansen <jacob@melon.dk>
To: Xen list <xen-devel@lists.sourceforge.net>
Subject: Forwarding page faults from within Xen
Date: Mon, 22 Mar 2004 12:36:23 +0100 [thread overview]
Message-ID: <1079955383.907.25.camel@paleface> (raw)
hi,
in my work on live-migration I often need to write-protect domain pages.
Until now, I have taken special care of pages which Xen needs to write,
for instance current->thread.esp0, and page tables mapping network
buffers, as otherwise Xen will just kill my domain upon write fault.
This is becoming a bit of a hassle, so I am wondering if it would be
possible for Xen to simply forward page faults to the faulting domain
(microkernel style) instead of killing it?
I am probably going to try and implement this myself, unless someone can
tell me why this is a horrible idea.
Jacob
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next reply other threads:[~2004-03-22 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 11:36 Jacob Gorm Hansen [this message]
2004-03-22 11:51 ` Forwarding page faults from within Xen Keir Fraser
2004-03-22 12:01 ` Jacob Gorm Hansen
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=1079955383.907.25.camel@paleface \
--to=jacob@melon.dk \
--cc=xen-devel@lists.sourceforge.net \
/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.