From: 陳韋任 <chenwj@iis.sinica.edu.tw>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, 陳韋任 <chenwj@iis.sinica.edu.tw>
Subject: Re: [Qemu-devel] Improve QEMU performance with LLVM codegen and other techniques
Date: Thu, 1 Dec 2011 17:25:03 +0800 [thread overview]
Message-ID: <20111201092503.GA24603@cs.nctu.edu.tw> (raw)
In-Reply-To: <CAMo8BfLBsOqnS+3RLBPP_M448ujeTHENDtss1rmQJQWMi_bitA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1423 bytes --]
Hi, Max
On Thu, Dec 01, 2011 at 12:15:06PM +0300, Max Filippov wrote:
> > 瓱isgenerated code might not be an issue now since we have tested our framework
> > in LLVM-only mode. I think the problem still is about the link/unlink stuff.
> > The first problem I have while lowering the threshold is the broken one generate
> > a few traces (2, actually) that a work one doesn't. When boot the linux image
> > downloaded from the QEMU website, the system hangs on the booting process (see
> > attach if you're interested). Simply put, the system hangs after printing
>
> 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?
> > ?..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?
Thanks!
Regards,
chenwj
--
Wei-Ren Chen (陳韋任)
Computer Systems Lab, Institute of Information Science,
Academia Sinica, Taiwan (R.O.C.)
Tel:886-2-2788-3799 #1667
Homepage: http://people.cs.nctu.edu.tw/~chenwj
[-- Attachment #2: system_hang.png --]
[-- Type: image/png, Size: 138996 bytes --]
next prev parent reply other threads:[~2011-12-01 9:25 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 ` 陳韋任 [this message]
2011-12-01 9:41 ` Max Filippov
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=20111201092503.GA24603@cs.nctu.edu.tw \
--to=chenwj@iis.sinica.edu.tw \
--cc=jcmvbkbc@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.