[Qemu-devel] Fwd: Re: QEMU+Aarch64: in_asm log skips instructions of loop-programs

[Qemu-devel] Fwd: Re: QEMU+Aarch64: in_asm log skips instructions of loop-programs

[Sergey Smolov]

[-- 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 --]

Re: [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of loop-programs

[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).

>  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

Re: [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of loop-programs

[Sergey Smolov]

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

Re: [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of loop-programs

[Sergey Smolov]

>
> 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

Re: [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of loop-programs

[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

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

Re: [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of loop-programs

[Sergey Smolov]

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

Re: [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of loop-programs

[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

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

Re: [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of loop-programs

[Sergey Smolov]

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
>