From: Rik van Riel <riel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Izik Eidus <izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: andrea-atKUWr5tajBWk0Htik3J/w@public.gmane.org,
yaniv-atKUWr5tajBWk0Htik3J/w@public.gmane.org,
kvm-devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org
Subject: Re: [RFC][PATCH 0/5] Memory merging driver for Linux
Date: Wed, 23 Jan 2008 12:05:10 -0500 [thread overview]
Message-ID: <20080123120510.4014e382@bree.surriel.com> (raw)
In-Reply-To: <4794C2E1.8040607-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
On Mon, 21 Jan 2008 18:05:53 +0200
Izik Eidus <izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
> i added 2 new functions to the kernel
> one:
> page_wrprotect() make the page as read only by setting the ptes point to
> it as read only.
> second:
> replace_page() - replace the pte mapping related to vm area between two
> pages
How will this work on CPUs with nested paging support, where the
CPU does the guest -> physical address translation? (opposed to
having shadow page tables)
Is it sufficient to mark the page read-only in the guest->physical
translation page table?
--
All rights reversed.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
WARNING: multiple messages have this Message-ID (diff)
From: Rik van Riel <riel@redhat.com>
To: Izik Eidus <izike@qumranet.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
andrea@qumranet.com, avi@qumranet.com, dor.laor@qumranet.com,
linux-mm@kvack.org, yaniv@qumranet.com
Subject: Re: [kvm-devel] [RFC][PATCH 0/5] Memory merging driver for Linux
Date: Wed, 23 Jan 2008 12:05:10 -0500 [thread overview]
Message-ID: <20080123120510.4014e382@bree.surriel.com> (raw)
In-Reply-To: <4794C2E1.8040607@qumranet.com>
On Mon, 21 Jan 2008 18:05:53 +0200
Izik Eidus <izike@qumranet.com> wrote:
> i added 2 new functions to the kernel
> one:
> page_wrprotect() make the page as read only by setting the ptes point to
> it as read only.
> second:
> replace_page() - replace the pte mapping related to vm area between two
> pages
How will this work on CPUs with nested paging support, where the
CPU does the guest -> physical address translation? (opposed to
having shadow page tables)
Is it sufficient to mark the page read-only in the guest->physical
translation page table?
--
All rights reversed.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-01-23 17:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 16:05 [RFC][PATCH 0/5] Memory merging driver for Linux Izik Eidus
2008-01-21 16:05 ` Izik Eidus
[not found] ` <4794C2E1.8040607-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-23 17:05 ` Rik van Riel [this message]
2008-01-23 17:05 ` [kvm-devel] " Rik van Riel
[not found] ` <20080123120510.4014e382-Fuq27k0DHcCSkoNiqTzCLQ@public.gmane.org>
2008-01-23 17:54 ` Andrea Arcangeli
2008-01-23 17:54 ` [kvm-devel] " Andrea Arcangeli
[not found] ` <20080123175444.GH7141-lysg2Xt5kKMAvxtiuMwx3w@public.gmane.org>
2008-01-23 18:11 ` Izik Eidus
2008-01-23 18:11 ` [kvm-devel] " Izik Eidus
2008-01-24 5:38 ` Avi Kivity
2008-01-24 5:38 ` [kvm-devel] " Avi Kivity
2008-01-23 23:10 ` Chris Wright
2008-01-23 23:10 ` [kvm-devel] " Chris Wright
[not found] ` <20080123231037.GA3629-JyIX8gxvWYPr2PDY2+4mTGD2FQJk+8+b@public.gmane.org>
2008-01-24 5:40 ` Avi Kivity
2008-01-24 5:40 ` [kvm-devel] " Avi Kivity
[not found] ` <479824EA.7070603-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-24 9:26 ` Izik Eidus
2008-01-24 9:26 ` [kvm-devel] " Izik Eidus
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=20080123120510.4014e382@bree.surriel.com \
--to=riel-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=andrea-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=yaniv-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
/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.