From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:40384)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jcmvbkbc@gmail.com>) id 1RW39T-0002gM-Oo
	for qemu-devel@nongnu.org; Thu, 01 Dec 2011 04:42:00 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jcmvbkbc@gmail.com>) id 1RW39S-0006zI-E4
	for qemu-devel@nongnu.org; Thu, 01 Dec 2011 04:41:59 -0500
Received: from mail-yw0-f45.google.com ([209.85.213.45]:36829)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jcmvbkbc@gmail.com>) id 1RW39S-0006zE-AP
	for qemu-devel@nongnu.org; Thu, 01 Dec 2011 04:41:58 -0500
Received: by ywe9 with SMTP id 9so2134474ywe.4
	for <qemu-devel@nongnu.org>; Thu, 01 Dec 2011 01:41:57 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <20111201092503.GA24603@cs.nctu.edu.tw>
References: <20111129070343.GA3585@cs.nctu.edu.tw>
	<CAFEAcA_hgt2nXBeBW5mi6n=PYzE0j6X-BfVyGsDKjee8Vts5cw@mail.gmail.com>
	<20111201090313.GB12949@cs.nctu.edu.tw>
	<CAMo8BfLBsOqnS+3RLBPP_M448ujeTHENDtss1rmQJQWMi_bitA@mail.gmail.com>
	<20111201092503.GA24603@cs.nctu.edu.tw>
Date: Thu, 1 Dec 2011 12:41:57 +0300
Message-ID: <CAMo8BfK0YhVnQnRFShBLhvp3hKJeQyoMLcPRONyFvTdpii7nrg@mail.gmail.com>
From: Max Filippov <jcmvbkbc@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] Improve QEMU performance with LLVM codegen and
	other techniques
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: =?UTF-8?B?6Zmz6Z+L5Lu7?= <chenwj@iis.sinica.edu.tw>
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org

>> There's no attachment in this mail. I can try to help you resolving it
>> if you provide more information.
>
> =A0Sorry about that, see the attachment please. What kind of information =
you want
> to know?

If your code is available online I can try it myself, the question is
where is it hosted then.
If not, then link to kernel binary and qemu exec trace would help me to sta=
rt.

>> > ?..TIMER: vector=3D0x31 apic1=3D0 pin1=3D2 apic2=3D-1 pin2=3D-1
>> >
>> > which turns out should be function check_timer (arch/i386/kernel/io_ap=
ic.c). I
>>
>> If it hangs inside QEMU itself then you may try to backport commit
>> 4f61927a41a098d06e642ffdea5fc285dc3a0e6b that fixes
>> infinite loop caused by hpet interrupt probing.
>
> =A0I don't understand. What "it hangs inside QEMU itself" supposed to mea=
n?

QEMU doesn't execute guest code doing something for itself vs. QEMU
executes guest code in loop checking for something that doesn't
happen.

I'm talking about the first case. They may be distinguished from e.g.
guest debugger connected to QEMU's gdbstub -- in the former case it
cannot break guest execution by ^C.

--=20
Thanks.
-- Max