From: Kip Macy <kmacy@fsmware.com>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: "Scheer, Roque" <roque.scheer@hp.com>, xen-devel@lists.sourceforge.net
Subject: Re: Seamlessly sharing identical memory pages among domains
Date: Thu, 20 May 2004 20:58:52 -0700 (PDT) [thread overview]
Message-ID: <20040520205407.Q70577@demos.bsdclusters.com> (raw)
In-Reply-To: <E1BQyfa-00055Y-00@mta1.cl.cam.ac.uk>
>
> Doing a proper shared cache is slightly trickier given the
> paravirtualised memory interface -- we'd have to introduce guests
> to a new kind of write fault: "A write fault has occurred, and
> you'll have to copy the page because this machine page is
> immutable as it is already shared with other domains". Modifying
> Linux to handle this wouldn't be hard.
Would this just involve adding an extra error code to what x86 already
uses and then modifying the guest to understand that that error code
means that the page has to be COWed?
-Kip
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
next prev parent reply other threads:[~2004-05-21 3:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 13:18 Seamlessly sharing identical memory pages among domains Scheer, Roque
2004-05-21 1:17 ` Ian Pratt
2004-05-21 3:58 ` Kip Macy [this message]
2004-05-21 6:56 ` Ian Pratt
2004-05-21 11:21 ` Kip Macy
2004-05-21 5:52 ` Niraj Tolia
-- strict thread matches above, loose matches on Subject: below --
2004-05-21 11:56 Scheer, Roque
2004-05-21 12:05 ` Ian Pratt
2004-05-21 12:08 ` Steven Hand
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=20040520205407.Q70577@demos.bsdclusters.com \
--to=kmacy@fsmware.com \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=roque.scheer@hp.com \
--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.