All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 6 Dec 2011 14:37:24 +0800	[thread overview]
Message-ID: <20111206063724.GA8299@cs.nctu.edu.tw> (raw)
In-Reply-To: <CAMo8BfK0YhVnQnRFShBLhvp3hKJeQyoMLcPRONyFvTdpii7nrg@mail.gmail.com>

Hi Max,

> 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.

  Personally, I really want to make our work public, but I am not the decision
maker. I'll push it toward open source however.
 
> >> > ?..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.
> >
> > 狢 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.

  It turns out this is our IBTC optimization problem [1]. The IBTC should take
cross page boundary constraint into consideration as block linking does (at
least in QEMU current design) [2].

  As I said before, we have two code caches in our framework: one for basic
block, the other for trace. I forgot to turn off trace's IBTC optimization as
it doesn't consider cross page boundary right now. As a workaround, we return to
QEMU (dispatcher) while doing IBTC lookup, and the problem I mentioned
disappeared. Sometimes I feel I am chaseing a ghost when debug our system. ;-)

[1] http://lists.gnu.org/archive/html/qemu-devel/2011-08/msg01424.html
[2] http://lists.nongnu.org/archive/html/qemu-devel/2011-08/msg02249.html

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

  reply	other threads:[~2011-12-06  6:37 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
2011-12-06  6:37           ` 陳韋任 [this message]
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=20111206063724.GA8299@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.