Prev: usb: gadget: #include device.h in gadget.h
Next: Retry fault before vmentry
From: Rik van Riel on 8 Jul 2010 00:30
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(a)redhat.com>

Acked-by: Rik van Riel <riel(a)redhat.com>

--
All rights reversed
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: usb: gadget: #include device.h in gadget.h
Next: Retry fault before vmentry