From: Max Filippov <jcmvbkbc@gmail.com>
To: 陳韋任 <chenwj@iis.sinica.edu.tw>
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Improve QEMU performance with LLVM codegen and other techniques
Date: Thu, 1 Dec 2011 12:41:57 +0300 [thread overview]
Message-ID: <CAMo8BfK0YhVnQnRFShBLhvp3hKJeQyoMLcPRONyFvTdpii7nrg@mail.gmail.com> (raw)
In-Reply-To: <20111201092503.GA24603@cs.nctu.edu.tw>
>> There's no attachment in this mail. I can try to help you resolving it
>> if you provide more information.
>
> Sorry 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 start.
>> > ?..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
>> >
>> > which turns out should be function check_timer (arch/i386/kernel/io_apic.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.
>
> I don't understand. What "it hangs inside QEMU itself" supposed to mean?
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.
--
Thanks.
-- Max
next prev parent reply other threads:[~2011-12-01 9:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 7:03 [Qemu-devel] Improve QEMU performance with LLVM codegen and other techniques 陳韋任
2011-11-30 12:37 ` Alexander Graf
2011-12-01 3:50 ` 陳韋任
2011-12-01 7:46 ` Stefan Hajnoczi
2011-12-01 9:16 ` Alex Bradbury
2011-12-01 9:30 ` 陳韋任
2011-12-01 10:23 ` Alexander Graf
2011-12-04 6:14 ` 陳韋任
2011-12-04 11:29 ` Alexander Graf
2011-12-05 6:05 ` 陳韋任
2011-12-01 10:59 ` Peter Maydell
2011-12-06 7:39 ` 陳韋任
2011-12-19 17:44 ` Alexander Graf
2011-11-30 12:51 ` Peter Maydell
2011-12-01 9:03 ` 陳韋任
2011-12-01 9:13 ` 陳韋任
2011-12-01 9:15 ` Max Filippov
2011-12-01 9:25 ` 陳韋任
2011-12-01 9:41 ` Max Filippov [this message]
2011-12-06 6:37 ` 陳韋任
2011-12-01 10:12 ` Peter Maydell
2011-12-01 10:40 ` 陳韋任
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMo8BfK0YhVnQnRFShBLhvp3hKJeQyoMLcPRONyFvTdpii7nrg@mail.gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=chenwj@iis.sinica.edu.tw \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).