linux-kernel - Re: [patch 1/6] Guest page hinting: core + volatile page cache.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5056.1178894723@turing-police.cc.vt.edu>
Date:	Fri, 11 May 2007 10:45:23 -0400
From:	Valdis.Kletnieks@...edu
To:	Martin Schwidefsky <schwidefsky@...ibm.com>
Cc:	virtualization@...ts.osdl.org, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, Zachary Amsden <zach@...are.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Nick Piggin <npiggin@...e.de>,
	Hubertus Franke <frankeh@...son.ibm.com>,
	Rik van Riel <riel@...hat.com>
Subject: Re: [patch 1/6] Guest page hinting: core + volatile page cache.

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?

Content of type "application/pgp-signature" skipped