On 14.04.14 10:08, liu ping fan wrote:
On Mon, Apr 14, 2014 at 2:43 PM, Alexander Graf wrote:
On 13.04.14 04:27, Liu ping fan wrote:
On Fri, Apr 11, 2014 at 10:03 PM, Alexander Graf wrote:
On 11.04.2014, at 13:45, Liu Ping Fan
wrote:
When we mark pte with _PAGE_NUMA we already call
mmu_n
On Mon, Apr 14, 2014 at 2:43 PM, Alexander Graf wrote:
>
> On 13.04.14 04:27, Liu ping fan wrote:
>>
>> On Fri, Apr 11, 2014 at 10:03 PM, Alexander Graf wrote:
>>>
>>> On 11.04.2014, at 13:45, Liu Ping Fan
>>> wrote:
>>>
When we mark pte with _PAGE_NUMA we already call
mmu_notifier_inv
On 13.04.14 04:27, Liu ping fan wrote:
On Fri, Apr 11, 2014 at 10:03 PM, Alexander Graf wrote:
On 11.04.2014, at 13:45, Liu Ping Fan wrote:
When we mark pte with _PAGE_NUMA we already call
mmu_notifier_invalidate_range_start
and mmu_notifier_invalidate_range_end, which will mark existing g
On Fri, Apr 11, 2014 at 10:03 PM, Alexander Graf wrote:
>
> On 11.04.2014, at 13:45, Liu Ping Fan wrote:
>
>> When we mark pte with _PAGE_NUMA we already call
>> mmu_notifier_invalidate_range_start
>> and mmu_notifier_invalidate_range_end, which will mark existing guest hpte
>> entry as HPTE_V_A
On 11.04.2014, at 13:45, Liu Ping Fan wrote:
> When we mark pte with _PAGE_NUMA we already call
> mmu_notifier_invalidate_range_start
> and mmu_notifier_invalidate_range_end, which will mark existing guest hpte
> entry as HPTE_V_ABSENT. Now we need to do that when we are inserting new
> guest h
When we mark pte with _PAGE_NUMA we already call
mmu_notifier_invalidate_range_start
and mmu_notifier_invalidate_range_end, which will mark existing guest hpte
entry as HPTE_V_ABSENT. Now we need to do that when we are inserting new
guest hpte entries.
Signed-off-by: Liu Ping Fan
Reviewed-by: An