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:
pgpMG5TX3RCHW.pgp
Description: PGP signature
- Follow-Ups:
- Re: [patch 1/6] Guest page hinting: core + volatile page cache.
- From: Martin Schwidefsky <[email protected]>
- Re: [patch 1/6] Guest page hinting: core + volatile page cache.
- References:
- [patch 0/6] [rfc] guest page hinting version 5
- From: Martin Schwidefsky <[email protected]>
- [patch 1/6] Guest page hinting: core + volatile page cache.
- From: Martin Schwidefsky <[email protected]>
- [patch 0/6] [rfc] guest page hinting version 5
- Prev by Date: Re: [PATCH] make cancel_rearming_delayed_work() reliable
- Next by Date: Re: 2.6.21-git10/11: files getting truncated on xfs? or maybe an nlink problem?
- Previous by thread: [patch 1/6] Guest page hinting: core + volatile page cache.
- Next by thread: Re: [patch 1/6] Guest page hinting: core + volatile page cache.
- Index(es):
 |