qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Jun Koi <junkoi2004@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] flush TB on singlestep command
Date: Wed, 28 Apr 2010 20:06:36 +0200	[thread overview]
Message-ID: <4BD8792C.3050509@mail.berlios.de> (raw)
In-Reply-To: <j2ofdaac4d51004271650qdb3f5994q2600861b8487f87@mail.gmail.com>

Am 28.04.2010 01:50, schrieb Jun Koi:
> On Wed, Apr 28, 2010 at 4:55 AM, Stefan Weil <weil@mail.berlios.de> wrote:
>> Typical use case: execution trace of some code which is
>> run after OS boot with an explicit trigger.
>>
>> This can be loading of a linux kernel module, a user space
>> application or kernel code which handles a rare event.
>>
>> I can enable logging and single stepping before that code
>> starts. There is no need to re-translate existing TBs:
>> they are faster than TBs with only single steps, so only
>> the execution of the new code is slow, and only new TBs
>> will appear in qemu.log which is exactly what I want.
>>
>> Typically, I use single stepping like this to examine a
>> problem with QEMU's emulation or code generation. Two examples:
>> some years ago aptitude crashed in mips emulation (fpu emulation
>> problem), and now I use it to examine differences between
>> native TCG and TCI (tiny code interpreter).
>
> What is that TCI???
>
> Thanks,
> J


TCI stands for Tiny Code Interpreter and is a new way
to run QEMU's Tiny Code. Links with more information:

http://lists.gnu.org/archive/html/qemu-devel/2009-09/msg01710.html
http://repo.or.cz/w/qemu/ar7.git/blob_plain/master:/tcg/bytecode/README

Regards,
Stefan

  reply	other threads:[~2010-04-28 18:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-16  1:03 [Qemu-devel] [PATCH] flush TB on singlestep command Jun Koi
2010-04-16 21:13 ` Stefan Weil
2010-04-20  1:17   ` Jun Koi
2010-04-20  7:18     ` [Qemu-devel] " Jan Kiszka
2010-04-20 10:51       ` Alexander Graf
2010-04-20 11:38         ` Jan Kiszka
2010-04-20 11:44           ` Alexander Graf
2010-04-21 10:04             ` Jun Koi
2010-04-21 10:11               ` Alexander Graf
2010-04-21 10:43                 ` Jan Kiszka
2010-04-21 19:20                   ` Stefan Weil
2010-04-22  7:02                     ` Jan Kiszka
2010-04-27 19:55                       ` Stefan Weil
2010-04-27 23:50                         ` Jun Koi
2010-04-28 18:06                           ` Stefan Weil [this message]
2010-04-22  7:14                     ` Jun Koi

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=4BD8792C.3050509@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=junkoi2004@gmail.com \
    --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).