Re: [PATCH RFC v2 4/6] KVM: change mark_page_dirty() to handle endian issues explicitly

On 04/20/2010 02:00 PM, Takuya Yoshikawa wrote: We are now using generic___set_le_bit() to make dirty bitmaps le. Though this works well, we have to replace __set_bit() to appropriate uaccess function to move dirty bitmaps to user space. So this patch splits generic___set_le_bit() and prepares fo

Re: [PATCH RFC v2 4/6] KVM: change mark_page_dirty() to handle endian issues explicitly

(2010/04/20 20:00), Alexander Graf wrote: On 20.04.2010, at 13:00, Takuya Yoshikawa wrote: We are now using generic___set_le_bit() to make dirty bitmaps le. Though this works well, we have to replace __set_bit() to appropriate uaccess function to move dirty bitmaps to user space. So this patch

Re: [PATCH RFC v2 4/6] KVM: change mark_page_dirty() to handle endian issues explicitly

On 20.04.2010, at 13:00, Takuya Yoshikawa wrote: > We are now using generic___set_le_bit() to make dirty bitmaps le. > Though this works well, we have to replace __set_bit() to appropriate > uaccess function to move dirty bitmaps to user space. So this patch > splits generic___set_le_bit() and pr

[PATCH RFC v2 4/6] KVM: change mark_page_dirty() to handle endian issues explicitly

We are now using generic___set_le_bit() to make dirty bitmaps le. Though this works well, we have to replace __set_bit() to appropriate uaccess function to move dirty bitmaps to user space. So this patch splits generic___set_le_bit() and prepares for that. Signed-off-by: Takuya Yoshikawa Signed-o