From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44273) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zcwcc-0004Y9-4w for qemu-devel@nongnu.org; Fri, 18 Sep 2015 10:26:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZcwcW-0004TD-Q6 for qemu-devel@nongnu.org; Fri, 18 Sep 2015 10:26:42 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:38265) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZcwcW-0004Sd-Ih for qemu-devel@nongnu.org; Fri, 18 Sep 2015 10:26:36 -0400 Message-ID: <55FC1F18.8040009@codeaurora.org> Date: Fri, 18 Sep 2015 10:26:32 -0400 From: Christopher Covington MIME-Version: 1.0 References: <7cd03581b882e28ef904a35a4ce1e374@ispras.ru> <55E859BA.8080502@ispras.ru> <55E93C0E.4000401@ispras.ru> <55E9C90E.8020408@ispras.ru> <55FB3881.5070608@codeaurora.org> <55FBC817.4040706@ispras.ru> In-Reply-To: <55FBC817.4040706@ispras.ru> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of loop-programs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Sergey Smolov Cc: Peter Maydell , QEMU Developers , Richard Henderson On 09/18/2015 04:15 AM, Sergey Smolov wrote: > Hi Christopher, >=20 > 18.09.2015 02:02, Christopher Covington =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> Hi Sergey, >> >> On 09/04/2015 12:38 PM, Sergey Smolov wrote: >>>> 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 wrot= e: >>>>>> 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 instruct= ions 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 implementatio= n? > 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 --=20 Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum= , a Linux Foundation Collaborative Project