On Sat, Aug 03, 2013 at 02:09:43PM +0900, Takuya Yoshikawa wrote:
> On Tue, 30 Jul 2013 21:01:58 +0800
> Xiao Guangrong wrote:
>
> > Background
> > ==
> > Currently, when mark memslot dirty logged or get dirty page, we need to
> > write-protect large guest memory, it is the heavy work,
On Sat, Aug 03, 2013 at 02:09:43PM +0900, Takuya Yoshikawa wrote:
On Tue, 30 Jul 2013 21:01:58 +0800
Xiao Guangrong xiaoguangr...@linux.vnet.ibm.com wrote:
Background
==
Currently, when mark memslot dirty logged or get dirty page, we need to
write-protect large guest memory, it
On 08/09/2013 01:38 AM, Paolo Bonzini wrote:
> Il 06/08/2013 15:16, Xiao Guangrong ha scritto:
>> Hi Gleb, Paolo, Marcelo, Takuya,
>>
>> Any comments or further comments? :)
>
> It's not the easiest patch to review. I've looked at it (beyond the
> small comments I have already posted), but it
Il 06/08/2013 15:16, Xiao Guangrong ha scritto:
> Hi Gleb, Paolo, Marcelo, Takuya,
>
> Any comments or further comments? :)
It's not the easiest patch to review. I've looked at it (beyond the
small comments I have already posted), but it will take some time to
digest it...
By the way, both I
Il 06/08/2013 15:16, Xiao Guangrong ha scritto:
Hi Gleb, Paolo, Marcelo, Takuya,
Any comments or further comments? :)
It's not the easiest patch to review. I've looked at it (beyond the
small comments I have already posted), but it will take some time to
digest it...
By the way, both I and
On 08/09/2013 01:38 AM, Paolo Bonzini wrote:
Il 06/08/2013 15:16, Xiao Guangrong ha scritto:
Hi Gleb, Paolo, Marcelo, Takuya,
Any comments or further comments? :)
It's not the easiest patch to review. I've looked at it (beyond the
small comments I have already posted), but it will take
Hi Gleb, Paolo, Marcelo, Takuya,
Any comments or further comments? :)
On 07/30/2013 09:01 PM, Xiao Guangrong wrote:
> Background
> ==
> Currently, when mark memslot dirty logged or get dirty page, we need to
> write-protect large guest memory, it is the heavy work, especially, we need to
Hi Gleb, Paolo, Marcelo, Takuya,
Any comments or further comments? :)
On 07/30/2013 09:01 PM, Xiao Guangrong wrote:
Background
==
Currently, when mark memslot dirty logged or get dirty page, we need to
write-protect large guest memory, it is the heavy work, especially, we need to
On Aug 3, 2013, at 1:09 PM, Takuya Yoshikawa wrote:
> On Tue, 30 Jul 2013 21:01:58 +0800
> Xiao Guangrong wrote:
>
>> Background
>> ==
>> Currently, when mark memslot dirty logged or get dirty page, we need to
>> write-protect large guest memory, it is the heavy work, especially, we
On Aug 3, 2013, at 1:09 PM, Takuya Yoshikawa takuya.yoshik...@gmail.com wrote:
On Tue, 30 Jul 2013 21:01:58 +0800
Xiao Guangrong xiaoguangr...@linux.vnet.ibm.com wrote:
Background
==
Currently, when mark memslot dirty logged or get dirty page, we need to
write-protect large guest
On Tue, 30 Jul 2013 21:01:58 +0800
Xiao Guangrong wrote:
> Background
> ==
> Currently, when mark memslot dirty logged or get dirty page, we need to
> write-protect large guest memory, it is the heavy work, especially, we need to
> hold mmu-lock which is also required by vcpu to fix its
On Tue, 30 Jul 2013 21:01:58 +0800
Xiao Guangrong xiaoguangr...@linux.vnet.ibm.com wrote:
Background
==
Currently, when mark memslot dirty logged or get dirty page, we need to
write-protect large guest memory, it is the heavy work, especially, we need to
hold mmu-lock which is also
Background
==
Currently, when mark memslot dirty logged or get dirty page, we need to
write-protect large guest memory, it is the heavy work, especially, we need to
hold mmu-lock which is also required by vcpu to fix its page table fault and
mmu-notifier when host page is being changed. In
Background
==
Currently, when mark memslot dirty logged or get dirty page, we need to
write-protect large guest memory, it is the heavy work, especially, we need to
hold mmu-lock which is also required by vcpu to fix its page table fault and
mmu-notifier when host page is being changed. In
14 matches
Mail list logo
