On Feb 25, 2017, at 10:03 PM, Pranith Kumar wrote:
> On Sat, Feb 25, 2017 at 8:46 PM, Programmingkid
> wrote:
>>
>>
>> With the i386 target, I did see host CPU usage go up to 120%. That was nice
>> to see. Windows XP and Windows 2000 would not boot to the desktop for some
>> reason.
>
> For w
On Sat, Feb 25, 2017 at 8:46 PM, Programmingkid
wrote:
>
>
> With the i386 target, I did see host CPU usage go up to 120%. That was nice
> to see. Windows XP and Windows 2000 would not boot to the desktop for some
> reason.
For windows XP, you need the patch here:
http://patchwork.ozlabs.org/patc
On Feb 24, 2017, at 1:37 PM, Alex Bennée wrote:
>
> G 3 writes:
>
>> Hi I was wondering if your MTTCG patches have been tested with a
>> PowerPC guest yet.
>
> You would have to talk to PPC guys about the current status of MTTCG for
> the PowerPC architecture. You can force it to run with -ac
G 3 writes:
> Hi I was wondering if your MTTCG patches have been tested with a
> PowerPC guest yet.
You would have to talk to PPC guys about the current status of MTTCG for
the PowerPC architecture. You can force it to run with -accel
tcg,thread=multi but it will likely behave weirdly if the at
Hi I was wondering if your MTTCG patches have been tested with a
PowerPC guest yet. Also do you have a repo someone could clone to
test out all your patches?
Richard Henderson writes:
> On 02/24/2017 05:29 AM, Alex Bennée wrote:
>> Hi Richard/Peter,
>>
>> Well obviously it was expecting a bit much for v13 to pass with flying
>> colours. A merge failure which didn't affect ARM caused the
>> regressions on other platforms resulting in the iothread not
On 02/24/2017 05:29 AM, Alex Bennée wrote:
Hi Richard/Peter,
Well obviously it was expecting a bit much for v13 to pass with flying
colours. A merge failure which didn't affect ARM caused the
regressions on other platforms resulting in the iothread not being
released during cpu_handle_interrupt.
Hi Richard/Peter,
Well obviously it was expecting a bit much for v13 to pass with flying
colours. A merge failure which didn't affect ARM caused the
regressions on other platforms resulting in the iothread not being
released during cpu_handle_interrupt. This fix has been merged into
Jan's drop glo
