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, Serg
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 wrote:
>> Do you thi
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 wrote:
Do you think it is possible to implement another QEMU logger which will
make a rec
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 wrote:
Do you think it is possible to implement another QEMU logger which will
make a record for every executed block,
>>> Yes (this wo
03.09.2015 19:35, Peter Maydell пишет:
On 3 September 2015 at 15:31, Sergey Smolov 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 p
03.09.2015 19:35, Peter Maydell пишет:
On 3 September 2015 at 15:31, Sergey Smolov 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 pr
On 3 September 2015 at 15:31, Sergey Smolov 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
th
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~
03.09.2015 10:33, Peter Maydell пишет:
On 3 September 2015 at 06:27, Sergey Smolov wrote:
I mean that in this example QEMU does not write to log "intermediate" SUBS
instructions which appear in loop-unrolling process.
For me it woulb be ok if QEMU generate the following in_asm log:
[log]
IN:
On 3 September 2015 at 06:27, Sergey Smolov wrote:
> I mean that in this example QEMU does not write to log "intermediate" SUBS
> instructions which appear in loop-unrolling process.
> For me it woulb be ok if QEMU generate the following in_asm log:
>
> [log]
> IN:
> 0x: 9401
Peter Maydell писал 2015-09-02 19:39:
On 2 September 2015 at 14:50, Sergey Smolov wrote:
02.09.2015 16:55, Sergey Smolov пишет:
It seems that QEMU skips some internal instructions when generates
"in_asm" log. How to eliminate this?
It might help if you said what you thought was missing.
--
On 2 September 2015 at 14:50, Sergey Smolov wrote:
> 02.09.2015 16:55, Sergey Smolov пишет:
>> It seems that QEMU skips some internal instructions when generates
>> "in_asm" log. How to eliminate this?
It might help if you said what you thought was missing.
-- PMM
Hello, List!
I've found that while running Aarch64 assembler programs on QEMU with
"-d in_asm" option enabled I receive not complete logs. For example, on
the following assembler program which contains a loop :
[assembler]
.globl _start
bl _start
_start:
label1:
movz x0, 10
subs x0, x0,
02.09.2015 16:55, Sergey Smolov пишет:
Hello, List!
I've found that while running Aarch64 assembler programs on QEMU with
"-d in_asm" option enabled I receive not complete logs. For example,
on the following assembler program which contains a loop :
[assembler]
.globl _start
bl _start
_start
14 matches
Mail list logo
