Looks like I missed an important discussion once again :) In the future
don't hesitate to put me in copy for Windows and or IO loop subjects.
On 02/21/2013 09:13 AM, Roy Tam wrote:
> 2013/2/21 Roy Tam :
>> 2013/2/21 Paolo Bonzini :
>>> Il 21/02/2013 01:35, Roy Tam ha scritto:
>> QEMU system e
2013/2/21 Paolo Bonzini :
> Il 21/02/2013 09:13, Roy Tam ha scritto:
>>> >
>>> > Yes, at least linux kernel starts but stalls when hitting IO-APIC
>>> > thingy, with noapic boot switch it stalls after detecting ttyS0
>>> >
>>> > With patch, QEMU is unresponsive when loading vmlinuz (not even
>>> >
Il 21/02/2013 09:13, Roy Tam ha scritto:
>> >
>> > Yes, at least linux kernel starts but stalls when hitting IO-APIC
>> > thingy, with noapic boot switch it stalls after detecting ttyS0
>> >
>> > With patch, QEMU is unresponsive when loading vmlinuz (not even
>> > showing "Decompressing Linux" mess
2013/2/21 Roy Tam :
> 2013/2/21 Paolo Bonzini :
>> Il 21/02/2013 01:35, Roy Tam ha scritto:
> QEMU system emulation has been thread-safe for a long time, and
> setting the CPU affinity is hurting performance badly. Remove
> the bogus code.
>
> Jacob Kroon reports that the
2013/2/21 Paolo Bonzini :
> Il 21/02/2013 01:35, Roy Tam ha scritto:
>>> > QEMU system emulation has been thread-safe for a long time, and
>>> > setting the CPU affinity is hurting performance badly. Remove
>>> > the bogus code.
>>> >
>>> > Jacob Kroon reports that the time to boot his VxWorks ima
Il 21/02/2013 01:35, Roy Tam ha scritto:
>> > QEMU system emulation has been thread-safe for a long time, and
>> > setting the CPU affinity is hurting performance badly. Remove
>> > the bogus code.
>> >
>> > Jacob Kroon reports that the time to boot his VxWorks image goes from
>> > "3 minutes pass
2013/2/20 Paolo Bonzini :
> QEMU system emulation has been thread-safe for a long time, and
> setting the CPU affinity is hurting performance badly. Remove
> the bogus code.
>
> Jacob Kroon reports that the time to boot his VxWorks image goes from
> "3 minutes passed and I still haven't made it th
Am 20.02.2013 15:49, schrieb Peter Maydell:
> On 20 February 2013 14:43, Laszlo Ersek wrote:
>> On 02/20/13 14:43, Paolo Bonzini wrote:
>>> QEMU system emulation has been thread-safe for a long time
>
> Says who? cpu_interrupt() calls tcg_handle_interrupt()
> which calls cpu_unlink_tb() which mak
On 20 February 2013 14:59, Paolo Bonzini wrote:
> Il 20/02/2013 15:49, Peter Maydell ha scritto:
>> On 20 February 2013 14:43, Laszlo Ersek wrote:
>>> On 02/20/13 14:43, Paolo Bonzini wrote:
QEMU system emulation has been thread-safe for a long time
>>
>> Says who? cpu_interrupt() calls tcg_
Il 20/02/2013 15:49, Peter Maydell ha scritto:
> On 20 February 2013 14:43, Laszlo Ersek wrote:
>> On 02/20/13 14:43, Paolo Bonzini wrote:
>>> QEMU system emulation has been thread-safe for a long time
>
> Says who? cpu_interrupt() calls tcg_handle_interrupt()
> which calls cpu_unlink_tb() which
On 20 February 2013 14:43, Laszlo Ersek wrote:
> On 02/20/13 14:43, Paolo Bonzini wrote:
>> QEMU system emulation has been thread-safe for a long time
Says who? cpu_interrupt() calls tcg_handle_interrupt()
which calls cpu_unlink_tb() which makes changes to the
TB datastructure with no kind of loc
On 02/20/13 14:43, Paolo Bonzini wrote:
> QEMU system emulation has been thread-safe for a long time, and
> setting the CPU affinity is hurting performance badly. Remove
> the bogus code.
>
> Jacob Kroon reports that the time to boot his VxWorks image goes from
> "3 minutes passed and I still hav
QEMU system emulation has been thread-safe for a long time, and
setting the CPU affinity is hurting performance badly. Remove
the bogus code.
Jacob Kroon reports that the time to boot his VxWorks image goes from
"3 minutes passed and I still haven't made it that far" to ~140s.
Cc: qemu-sta...@no
13 matches
Mail list logo
