Greetings,
the circus is back in town -- another version of the guest page hinting
patches. The patches differ from version 6 only in the kernel version,
they apply against 2.6.29. My short sniff test showed that the code
is still working as expected.
To recap (you can skip this if you read the
From: Martin Schwidefsky schwidef...@de.ibm.com
From: Hubertus Franke fran...@watson.ibm.com
From: Himanshu Raj
The volatile state for page cache and swap cache pages requires that
the host system needs to be able to determine if a volatile page is
dirty before removing it. This excludes almost
From: Martin Schwidefsky schwidef...@de.ibm.com
From: Hubertus Franke fran...@watson.ibm.com
From: Himanshu Raj
s390 uses the milli-coded ESSA instruction to set the page state. The
page state is formed by four guest page states called block usage states
and three host page states called block
From: Martin Schwidefsky schwidef...@de.ibm.com
From: Hubertus Franke fran...@watson.ibm.com
From: Himanshu Raj
Add code to get mlock() working with guest page hinting. The problem
with mlock is that locked pages may not be removed from page cache.
That means they need to be stable.
Rusty Russell wrote:
You can't just do this in tlb flush?
I don't think so. The problem is that lguest tracks 4 toplevels, using random
replacement. This cache is indexed by cr3 value.
Lguest assumes it's told about all pte removals or changes, but simple
additions get faulted in.
From: Martin Schwidefsky schwidef...@de.ibm.com
From: Hubertus Franke fran...@watson.ibm.com
From: Himanshu Raj
On of the challenges of the guest page hinting scheme is the cost for
the state transitions. If the cost gets too high the whole concept of
page state information is in question.
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
