On 03/06/2017 10:43 AM, Alex Bennée wrote:
>
> Frederic Konrad writes:
>
>> Hi All,
>>
>> I've a strangeness with the "drop iolock" patch.
>> It seems it has an impact on the MMIO execution patch-set I'm working
>> on:
>
> Hmm the only real change is the BQL (implicit or explict) being taken on
Frederic Konrad writes:
> Hi All,
>
> I've a strangeness with the "drop iolock" patch.
> It seems it has an impact on the MMIO execution patch-set I'm working
> on:
Hmm the only real change is the BQL (implicit or explict) being taken on
entry to the mmio functions.
> Basically modifying the m
Hi All,
I've a strangeness with the "drop iolock" patch.
It seems it has an impact on the MMIO execution patch-set I'm working
on:
Basically modifying the memory tree is causing a Bad Ram Address error.
I wonder if this can't happen with hotplug/unplug model as well.
I'll look into this.
Shoot i
Hi Peter,
So perhaps predictably the merging of MTTCG has thrown up some issues
during soft-freeze. The following patches fix up some of those:
The following where in v1 and just have r-b tags:
vl/cpus: be smarter with icount and MTTCG
target/i386/cpu.h: declare TCG_GUEST_DEFAULT_MO
cpus.c
