qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Covington <cov@codeaurora.org>
To: Sergey Smolov <smolov@ispras.ru>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of loop-programs
Date: Fri, 18 Sep 2015 10:26:32 -0400	[thread overview]
Message-ID: <55FC1F18.8040009@codeaurora.org> (raw)
In-Reply-To: <55FBC817.4040706@ispras.ru>

On 09/18/2015 04:15 AM, Sergey Smolov wrote:
> Hi Christopher,
> 
> 18.09.2015 02:02, Christopher Covington пишет:
>> Hi Sergey,
>>
>> On 09/04/2015 12:38 PM, Sergey Smolov wrote:
>>>> 03.09.2015 19:35, Peter Maydell пишет:
>>>>> On 3 September 2015 at 15:31, Sergey Smolov <smolov@ispras.ru> wrote:
>>>>>> Do you think it is possible to implement another QEMU logger which will
>>>>>> make a record for every executed block,
>>>>> Yes (this would just need to disable the TB linking optimisation,
>>>>> which we've discussed providing a debug toggle for in another
>>>>> thread).
>>> Ok, I've implemented a mapping between disassembled forms of instructions and
>>> executed TBs.
>>> Now my logger does "loop unrolling" successfully.
>> This sounds like it solves the same issue as -d nochain but in what's probably
>> a more time efficient manner. Are you able to share your implementation?

> In which way should I share it? Am I need to create a patch and send it to
> mailing list?

That would be ideal. If you're not familiar with the process, just let me know
and I'd be happy to help.

Thanks,
Christopher Covington

-- 
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2015-09-18 14:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7cd03581b882e28ef904a35a4ce1e374@ispras.ru>
2015-09-03 14:31 ` [Qemu-devel] Fwd: Re: QEMU+Aarch64: in_asm log skips instructions of loop-programs Sergey Smolov
2015-09-03 15:35   ` [Qemu-devel] " 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 [this message]
2015-11-03 12:15               ` Sergey Smolov
2015-09-02 12:55 Sergey Smolov
2015-09-02 13:50 ` Sergey Smolov
2015-09-02 16:39   ` Peter Maydell
2015-09-03  5:27     ` Sergey Smolov
2015-09-03  6:33       ` Peter Maydell
2015-09-03  7:09         ` Sergey Smolov
2015-09-03 14:28         ` Richard Henderson

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=55FC1F18.8040009@codeaurora.org \
    --to=cov@codeaurora.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=smolov@ispras.ru \
    /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).