From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:49795)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <smolov@ispras.ru>) id 1ZXur5-0004wq-CC
	for qemu-devel@nongnu.org; Fri, 04 Sep 2015 13:32:52 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <smolov@ispras.ru>) id 1ZXuqz-0001sa-TE
	for qemu-devel@nongnu.org; Fri, 04 Sep 2015 13:32:51 -0400
Received: from smtp.ispras.ru ([83.149.199.79]:42809)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <smolov@ispras.ru>) id 1ZXuqz-0001rN-Mx
	for qemu-devel@nongnu.org; Fri, 04 Sep 2015 13:32:45 -0400
References: <7cd03581b882e28ef904a35a4ce1e374@ispras.ru>
	<55E859BA.8080502@ispras.ru>
	<CAFEAcA-rgwwX70vtEQQNSoK_JeSUqeE6fhYFJoemoDx1K0BWCA@mail.gmail.com>
	<55E93C0E.4000401@ispras.ru>
From: Sergey Smolov <smolov@ispras.ru>
Message-ID: <55E9C90E.8020408@ispras.ru>
Date: Fri, 4 Sep 2015 20:38:38 +0400
MIME-Version: 1.0
In-Reply-To: <55E93C0E.4000401@ispras.ru>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of
 loop-programs
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Peter Maydell <peter.maydell@linaro.org>, Richard Henderson <rth@twiddle.net>
Cc: QEMU Developers <qemu-devel@nongnu.org>


>
> 03.09.2015 19:35, Peter Maydell =D0=BF=D0=B8=D1=88=D0=B5=D1=82:
>> 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 wi=
ll
>>> 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=20
instructions and executed TBs.
Now my logger does "loop unrolling" successfully.

Thank you very much for your help!

Sergey Smolov