On 12/16/2015 03:31 PM, Kai Huang wrote:
On 12/15/2015 05:03 PM, Xiao Guangrong wrote:
On 12/15/2015 04:11 PM, Kai Huang wrote:
On 12/01/2015 02:26 AM, Xiao Guangrong wrote:
The page fault caused by write access on the write tracked page can not
be fixed, it always need to be emulated. page_fault_handle_page_track()
is the fast path we introduce here to skip holding mmu-lock and shadow
page table walking
Why can it be out side of mmu-lock? Is it OK that some other thread removes
tracking of this page
simultaneously? Shall we assuming the emulation code should handle this case?
What your mentioned is the worst case, if that happen the vcpu will spend
longer time to emulate the access rather then retry it. It is bad but it is
the rare contention. It is worth speeding up the common / most case.
My concern is when this case happen, whether emulating the access is still the
right behavior, you
know, after other thread removed the GFN from tracking..
And as the notifier's track_write call back will be called in the emulating
code, won't there be
problem if the GFN has been removed from tracking by other thread?
When the notify callback is called, the tracker should check if the gfn is what
is interested by itself. If it sees the gfn is not trackered anymore, it can
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html