From: Valdis.Kletnieks@vt.edu
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: virtualization@lists.osdl.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Zachary Amsden <zach@vmware.com>,
Andrew Morton <akpm@linux-foundation.org>,
Nick Piggin <npiggin@suse.de>,
Hubertus Franke <frankeh@watson.ibm.com>,
Rik van Riel <riel@redhat.com>
Subject: Re: [patch 1/6] Guest page hinting: core + volatile page cache.
Date: Fri, 11 May 2007 10:45:23 -0400 [thread overview]
Message-ID: <5056.1178894723@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 11 May 2007 15:58:28 +0200." <20070511135925.513572897@de.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
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 where I don't see it, but IBM's
VM hypervisor supported reflecting page faults back to a multitasking guest,
giving a signal that the guest supervisor could use. The guest would then
look up which process owned that virtual page, and could elect to flag that
process as in page-wait and schedule another process to run while the hypervisor
was doing the I/O to bring the page in. The guest would then get another
interrupt when the page became available, which it could use to flag the
suspended process as eligible for scheduling again.
Not sure how that would fit into all this though - it looks like the
"discard fault" does something similar, but only for pages marked volatile.
Would it be useful/helpful to also deliver a similar signal for stable pages?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2007-05-11 14:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 13:58 [patch 0/6] [rfc] guest page hinting version 5 Martin Schwidefsky
2007-05-11 13:58 ` [patch 1/6] Guest page hinting: core + volatile page cache Martin Schwidefsky, Martin Schwidefsky, Hubertus Franke, Himanshu Raj
2007-05-11 14:45 ` Valdis.Kletnieks [this message]
2007-05-11 14:53 ` Martin Schwidefsky
2007-05-11 13:58 ` [patch 2/6] Guest page hinting: volatile swap cache Martin Schwidefsky, Martin Schwidefsky, Hubertus Franke, Himanshu Raj
2007-05-11 13:58 ` [patch 3/6] Guest page hinting: mlocked pages Martin Schwidefsky, Martin Schwidefsky, Hubertus Franke, Himanshu Raj
2007-05-11 13:58 ` [patch 4/6] Guest page hinting: writable page table entries Martin Schwidefsky, Martin Schwidefsky, Hubertus Franke, Himanshu Raj
2007-05-11 13:58 ` [patch 5/6] Guest page hinting: minor fault optimization Martin Schwidefsky, Martin Schwidefsky, Hubertus Franke, Himanshu Raj
2007-05-11 13:58 ` [patch 6/6] Guest page hinting: s390 support Martin Schwidefsky, Martin Schwidefsky, Hubertus Franke, Himanshu Raj
2007-06-28 16:40 [patch 0/6] resend: guest page hinting version 5 Martin Schwidefsky
2007-06-28 16:40 ` [patch 1/6] Guest page hinting: core + volatile page cache Martin Schwidefsky, Martin Schwidefsky, Hubertus Franke, Himanshu Raj
2009-03-27 15:09 [patch 0/6] Guest page hinting version 7 Martin Schwidefsky
2009-03-27 15:09 ` [patch 1/6] Guest page hinting: core + volatile page cache Martin Schwidefsky
2009-03-27 22:57 ` Rik van Riel
2009-03-29 13:56 ` Martin Schwidefsky
2009-03-29 14:35 ` Rik van Riel
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=5056.1178894723@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=frankeh@watson.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=riel@redhat.com \
--cc=schwidefsky@de.ibm.com \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox