From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: Mike Sun <msun@gatech.edu>
Cc: xen-devel@lists.xensource.com, Tim Deegan <Tim.Deegan@citrix.com>
Subject: Re: Fast checkpoints with COW VM memory
Date: Tue, 5 Feb 2008 10:39:50 +0000 [thread overview]
Message-ID: <20080205103950.GA4322@implementation.uk.xensource.com> (raw)
In-Reply-To: <e4e579070802041914y6564d2d0r7b9b9b9f1a0b6086@mail.gmail.com>
Mike Sun, le Mon 04 Feb 2008 22:14:26 -0500, a écrit :
> is there a way for me to determine if the protection fault is the
> result my my COW action as opposed to a protection fault actually
> incurred by the guest (i.e. perhaps the guest OS is implementing its
> own COW on portions of its memory)?
Not that I'm aware of.
> The only method I can think of is to keep track of the
> protection bits of the pages before I have the hypervisor modify them
> to read only,
Yes.
Samuel
prev parent reply other threads:[~2008-02-05 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 19:59 Fast checkpoints with COW VM memory Mike Sun
2007-12-05 22:05 ` Tim Deegan
2008-01-16 3:23 ` tgh
2008-01-16 4:28 ` Mike Sun
2008-02-05 3:14 ` Mike Sun
2008-02-05 10:39 ` Samuel Thibault [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=20080205103950.GA4322@implementation.uk.xensource.com \
--to=samuel.thibault@eu.citrix.com \
--cc=Tim.Deegan@citrix.com \
--cc=msun@gatech.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.