From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55637) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZXWOM-0001O5-Q2 for qemu-devel@nongnu.org; Thu, 03 Sep 2015 11:25:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZXWOI-00080I-Q5 for qemu-devel@nongnu.org; Thu, 03 Sep 2015 11:25:34 -0400 Received: from smtp.ispras.ru ([83.149.199.79]:41928) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZXWOI-0007zC-DD for qemu-devel@nongnu.org; Thu, 03 Sep 2015 11:25:30 -0400 References: <7cd03581b882e28ef904a35a4ce1e374@ispras.ru> From: Sergey Smolov Message-ID: <55E859BA.8080502@ispras.ru> Date: Thu, 3 Sep 2015 18:31:22 +0400 MIME-Version: 1.0 In-Reply-To: <7cd03581b882e28ef904a35a4ce1e374@ispras.ru> Content-Type: multipart/alternative; boundary="------------080102020802000706010305" Subject: [Qemu-devel] Fwd: Re: QEMU+Aarch64: in_asm log skips instructions of loop-programs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell , QEMU Developers This is a multi-part message in MIME format. --------------080102020802000706010305 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable -------- =D0=9F=D0=B5=D1=80=D0=B5=D0=BD=D0=B0=D0=BF=D1=80=D0=B0=D0=B2=D0=BB= =D0=B5=D0=BD=D0=BD=D0=BE=D0=B5 =D1=81=D0=BE=D0=BE=D0=B1=D1=89=D0=B5=D0=BD= =D0=B8=D0=B5 -------- =D0=A2=D0=B5=D0=BC=D0=B0: Re: [Qemu-devel] QEMU+Aarch64: in_asm log skip= s instructions of=20 loop-programs =D0=94=D0=B0=D1=82=D0=B0: Thu, 03 Sep 2015 18:22:16 +0300 =D0=9E=D1=82: Sergey Smolov =D0=9A=D0=BE=D0=BC=D1=83: Richard Henderson Richard Henderson =D0=BF=D0=B8=D1=81=D0=B0=D0=BB 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 --------------080102020802000706010305 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable


-------- =D0=9F=D0=B5=D1=80=D0=B5=D0=BD=D0=B0=D0=BF=D1=80=D0=B0=D0=B2= =D0=BB=D0=B5=D0=BD=D0=BD=D0=BE=D0=B5 =D1=81=D0=BE=D0=BE=D0=B1=D1=89=D0=B5= =D0=BD=D0=B8=D0=B5 --------
=D0= =A2=D0=B5=D0=BC=D0=B0: Re: [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of loop-programs
=D0= =94=D0=B0=D1=82=D0=B0: Thu, 03 Sep 2015 18:22:16 +0300
=D0= =9E=D1=82: Sergey Smolov <smolov@ispras.ru>
=D0= =9A=D0=BE=D0=BC=D1=83: Richard Henderson <rth@twiddle.net> 


Richard Henderson =D0=BF=D0=B8=D1=81=D0=B0=D0=BB 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.
>=20
> Even then you will of course only log the head of unlinked chains of=
=20
> blocks.
>=20
>=20
> r~

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

Thanks,

Sergey Smolov


--------------080102020802000706010305--