Martin Schwidefsky wrote:
On Fri, 27 Mar 2009 18:57:31 -0400
Rik van Riel r...@redhat.com wrote:
Martin Schwidefsky wrote:
There are some alternatives how this can be done, e.g. a global
lock, or lock per segment in the kernel page table, or the per page
bit PG_arch_1 if it is still
Martin Schwidefsky wrote:
The major obstacles that need to get addressed:
* Concurrent page state changes:
To guard against concurrent page state updates some kind of lock
is needed. If page_make_volatile() has already done the 11 checks it
will issue the state change primitive. If in
On Thu, 2008-03-13 at 10:12 +1100, Rusty Russell wrote:
On Thursday 13 March 2008 00:21:33 Martin Schwidefsky wrote:
@@ -957,6 +975,19 @@ struct page *follow_page(struct vm_area_
if (flags FOLL_GET)
get_page(page);
+
+ if (flags FOLL_GET) {
+ /*
+
On Thursday 13 March 2008 00:21:33 Martin Schwidefsky wrote:
@@ -957,6 +975,19 @@ struct page *follow_page(struct vm_area_
if (flags FOLL_GET)
get_page(page);
+
+ if (flags FOLL_GET) {
+ /*
+ * The page is made stable if a reference is
From: Martin Schwidefsky [EMAIL PROTECTED]
From: Hubertus Franke [EMAIL PROTECTED]
From: Himanshu Raj [EMAIL PROTECTED]
The guest page hinting patchset introduces code that passes guest
page usage information to the host system that virtualizes the
memory of its guests. There are three different
From: Martin Schwidefsky [EMAIL PROTECTED]
From: Hubertus Franke [EMAIL PROTECTED]
From: Himanshu Raj [EMAIL PROTECTED]
The guest page hinting patchset introduces code that passes guest
page usage information to the host system that virtualizes the
memory of its guests. There are three different
On Fri, 11 May 2007 15:58:28 +0200, Martin Schwidefsky said:
The guest page hinting patchset introduces code that passes guest
page usage information to the host system that virtualizes the
memory of its guests. There are three different page states:
Possibly hiding in the patchset someplace
On Fri, 2007-05-11 at 10:45 -0400, [EMAIL PROTECTED] wrote:
The guest page hinting patchset introduces code that passes guest
page usage information to the host system that virtualizes the
memory of its guests. There are three different page states:
Possibly hiding in the patchset
