All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Smolov <smolov@ispras.ru>
To: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Fwd: Re: QEMU+Aarch64: in_asm log skips instructions of loop-programs
Date: Thu, 3 Sep 2015 18:31:22 +0400	[thread overview]
Message-ID: <55E859BA.8080502@ispras.ru> (raw)
In-Reply-To: <7cd03581b882e28ef904a35a4ce1e374@ispras.ru>

[-- Attachment #1: Type: text/plain, Size: 834 bytes --]




-------- Перенаправленное сообщение --------
Тема: 	Re: [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of 
loop-programs
Дата: 	Thu, 03 Sep 2015 18:22:16 +0300
От: 	Sergey Smolov <smolov@ispras.ru>
Кому: 	Richard Henderson <rth@twiddle.net>



Richard Henderson писал 2015-09-03 17:28:
> On 09/02/2015 11:33 PM, Peter Maydell wrote:
>> You might find the 'exec' logging helpful for tracking
>> which translated blocks get executed.
>
> Even then you will of course only log the head of unlinked chains of
> blocks.
>
>
> r~

Do you think it is possible to implement another QEMU logger which will
make a record for every executed block, and these records will be in the
form of input assembler (in my case, Aarch64)?

Thanks,

Sergey Smolov




[-- Attachment #2: Type: text/html, Size: 1978 bytes --]

       reply	other threads:[~2015-09-03 15:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7cd03581b882e28ef904a35a4ce1e374@ispras.ru>
2015-09-03 14:31 ` Sergey Smolov [this message]
2015-09-03 15:35   ` [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of loop-programs Peter Maydell
2015-09-04  6:37     ` Sergey Smolov
2015-09-04 16:38       ` Sergey Smolov
2015-09-17 22:02         ` Christopher Covington
2015-09-18  8:15           ` Sergey Smolov
2015-09-18 14:26             ` Christopher Covington
2015-11-03 12:15               ` Sergey Smolov

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=55E859BA.8080502@ispras.ru \
    --to=smolov@ispras.ru \
    --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.