* [Qemu-devel] Fwd: Re: QEMU+Aarch64: in_asm log skips instructions of loop-programs [not found] <7cd03581b882e28ef904a35a4ce1e374@ispras.ru> @ 2015-09-03 14:31 ` Sergey Smolov 2015-09-03 15:35 ` [Qemu-devel] " Peter Maydell 0 siblings, 1 reply; 8+ messages in thread From: Sergey Smolov @ 2015-09-03 14:31 UTC (permalink / raw) To: Peter Maydell, QEMU Developers [-- 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 --] ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of loop-programs 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 ` Peter Maydell 2015-09-04 6:37 ` Sergey Smolov 0 siblings, 1 reply; 8+ messages in thread From: Peter Maydell @ 2015-09-03 15:35 UTC (permalink / raw) To: Sergey Smolov; +Cc: QEMU Developers 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). > and these records will be in the > form of input assembler (in my case, Aarch64)? No. At execution time we don't have the input assembler. You need to match up the TB addresses in the execution logs with the translation logs to find the input asm. thanks -- PMM ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of loop-programs 2015-09-03 15:35 ` [Qemu-devel] " Peter Maydell @ 2015-09-04 6:37 ` Sergey Smolov 2015-09-04 16:38 ` Sergey Smolov 0 siblings, 1 reply; 8+ messages in thread From: Sergey Smolov @ 2015-09-04 6:37 UTC (permalink / raw) To: Peter Maydell, Richard Henderson; +Cc: QEMU Developers 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). Sorry, are you talking about this patch: https://lists.gnu.org/archive/html/qemu-devel/2014-03/msg05603.html? Will this be added to QEMU master in the nearest future? Thanks, Sergey Smolov ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of loop-programs 2015-09-04 6:37 ` Sergey Smolov @ 2015-09-04 16:38 ` Sergey Smolov 2015-09-17 22:02 ` Christopher Covington 0 siblings, 1 reply; 8+ messages in thread From: Sergey Smolov @ 2015-09-04 16:38 UTC (permalink / raw) To: Peter Maydell, Richard Henderson; +Cc: QEMU Developers > > 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. Thank you very much for your help! Sergey Smolov ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of loop-programs 2015-09-04 16:38 ` Sergey Smolov @ 2015-09-17 22:02 ` Christopher Covington 2015-09-18 8:15 ` Sergey Smolov 0 siblings, 1 reply; 8+ messages in thread From: Christopher Covington @ 2015-09-17 22:02 UTC (permalink / raw) To: Sergey Smolov, Peter Maydell, Richard Henderson; +Cc: QEMU Developers 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? 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of loop-programs 2015-09-17 22:02 ` Christopher Covington @ 2015-09-18 8:15 ` Sergey Smolov 2015-09-18 14:26 ` Christopher Covington 0 siblings, 1 reply; 8+ messages in thread From: Sergey Smolov @ 2015-09-18 8:15 UTC (permalink / raw) To: Christopher Covington, Peter Maydell, Richard Henderson; +Cc: QEMU Developers 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? > > Thanks, > Christopher Covington > In which way should I share it? Am I need to create a patch and send it to mailing list? Sergey Smolov ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of loop-programs 2015-09-18 8:15 ` Sergey Smolov @ 2015-09-18 14:26 ` Christopher Covington 2015-11-03 12:15 ` Sergey Smolov 0 siblings, 1 reply; 8+ messages in thread From: Christopher Covington @ 2015-09-18 14:26 UTC (permalink / raw) To: Sergey Smolov; +Cc: Peter Maydell, QEMU Developers, Richard Henderson 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of loop-programs 2015-09-18 14:26 ` Christopher Covington @ 2015-11-03 12:15 ` Sergey Smolov 0 siblings, 0 replies; 8+ messages in thread From: Sergey Smolov @ 2015-11-03 12:15 UTC (permalink / raw) To: Christopher Covington; +Cc: Peter Maydell, QEMU Developers, Richard Henderson Hi Christopher, I've send my patch to the mailing list. Sorry for the great delay in answers. 18.09.2015 18:26, Christopher Covington пишет: > 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 > ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2015-11-03 13:14 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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
2015-11-03 12:15 ` Sergey Smolov
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.