On 07/06/2010 12:24 PM, Gleb Natapov wrote:
If guest can detect that it runs in non-preemptable context it can handle async PFs at any time, so let host know that it can send async PF even if guest cpu is not in userspace.
The code looks correct. One question though - is there a reason to implement the userspace-only async PF path at all, since the handling of async PF in non-userspace context is introduced simultaneously?
Signed-off-by: Gleb Natapov<gleb@xxxxxxxxxx>
Acked-by: Rik van Riel <riel@xxxxxxxxxx> -- All rights reversed -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>