Hollis Blanchard wrote:
> On Fri, 2007-12-14 at 10:07 +0100, Christian Ehrhardt wrote:
>> Hollis Blanchard wrote:
>>> A comment to explain why the icache needs flushing only in the KVM
>> case
>>> would be useful. Other than that I'm fine with it.
>>>
>>> Signed-off-by: Hollis Blanchard <[EMAIL PRO
On Fri, 2007-12-14 at 10:07 +0100, Christian Ehrhardt wrote:
>
> Hollis Blanchard wrote:
> > A comment to explain why the icache needs flushing only in the KVM
> case
> > would be useful. Other than that I'm fine with it.
> >
> > Signed-off-by: Hollis Blanchard <[EMAIL PROTECTED]>
> AFAIK Plain q
Christian Ehrhardt wrote:
> Zhang, Xiantao wrote:
>> Christian Ehrhardt wrote:
> <[...]
>>> @@ -2600,8 +2601,8 @@ void cpu_physical_memory_rw(target_phys_addr_t
>>> addr, uint8_t *buf, phys_ram_dirty[addr1 >>
>>> TARGET_PAGE_BITS] |= (0xff &
>>>
Zhang, Xiantao wrote:
>Christian Ehrhardt wrote:
<[...]
>> @@ -2600,8 +2601,8 @@ void cpu_physical_memory_rw(target_phys_addr_t
>> addr, uint8_t *buf, phys_ram_dirty[addr1 >>
>> TARGET_PAGE_BITS] |= (0xff &
>> ~CODE_DIRTY_FLAG); }
>> -#
> #include "qemu-kvm.h"
> #endif
> #if defined(CONFIG_USER_ONLY)
> @@ -2600,8 +2601,8 @@ void cpu_physical_memory_rw(target_phys_addr_t
> addr, uint8_t *buf, phys_ram_dirty[addr1 >>
> TARGET_PAGE_BITS] |= (0xff &
> ~CODE_DIRTY_FLAG)