From: Artyom Tarasenko <atar4qemu@googlemail.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: singlestep and sparc32
Date: Mon, 19 Apr 2010 22:33:00 +0200 [thread overview]
Message-ID: <q2zfb8d4f71004191333w45186ecq155452531af07565@mail.gmail.com> (raw)
In-Reply-To: <t2if43fc5581004191255x8192ffdat84fea59d237c1f71@mail.gmail.com>
2010/4/19 Blue Swirl <blauwirbel@gmail.com>:
> On 4/19/10, Artyom Tarasenko <atar4qemu@googlemail.com> wrote:
>> is -single-step option supposed to work under qemu-system-sparc? Or is
>> it only for non-pipelined CPUs?
>
> I've never used it.
is there another way to reduce a translation block? -icount 1 doesn't
make a difference.
>> I get pretty strange results: some addresses seem to be executed
>> twice, and then qemu hangs on the last nop:
>
> One possibility is that we don't generate any code at all for nops
> (sethi x, %g0). If you delete the "if (rd)" check in translate.c:1784,
> does it help?
Seems to make no difference at all.
>> --------------
>> IN:
>> 0x00000000: b 0xb788
>> --------------
>> IN:
>> 0x00000004: rd %psr, %l0
>> --------------
>> IN:
>> 0x00000004: rd %psr, %l0
>> --------------
>> IN:
>> 0x00000008: nop
>> --------------
>> IN:
>> 0x00000008: nop
>> --------------
>> IN:
>> 0x0000000c: nop
>> --------------
>> IN:
>> 0x0000000c: nop
>>
>> ... skipped ...
>>
>> IN:
>> 0x7000a58c: bg 0x7000a588
>> --------------
>> IN:
>> 0x7000a590: nop
>> --------------
>> IN:
>> 0x7000a590: nop
>> --------------
>> IN:
>> 0x7000a594: b 0x7000a570
>> --------------
>> IN:
>> 0x7000a594: b 0x7000a570
>> --------------
>> IN:
>> 0x7000a578: be 0x7000a59c
>> --------------
>> IN:
>> 0x7000a580: stba %l1, [ %l0 ] #ASI_M_BYPASS
>> --------------
>> IN:
>> 0x7000a588: deccc %l2
>> --------------
>> IN:
>> 0x7000a594: b 0x7000a570
>> --------------
>> IN:
>> 0x7000a590: nop
>>
>> ^^^^^^^^^^^ That's the end
>>
>> Without -singlestep it seems to work better:
>>
>>
>> 0x7000a588: deccc %l2
>> 0x7000a58c: bg 0x7000a588
>> 0x7000a590: nop
>>
>> --------------
>> IN:
>> 0x7000a594: b 0x7000a570
>> 0x7000a598: inc %l4
>>
>> --------------
>> IN:
>> 0x7000a570: lduba [ %l4 ] #ASI_M_KERNELTXT, %l1
>> 0x7000a574: cmp %l1, 0xff
>> 0x7000a578: be 0x7000a59c
>> ... and so on ...
--
Regards,
Artyom Tarasenko
solaris/sparc under qemu blog: http://tyom.blogspot.com/
prev parent reply other threads:[~2010-04-19 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 14:33 [Qemu-devel] singlestep and sparc32 Artyom Tarasenko
2010-04-19 16:07 ` malc
2010-04-19 16:19 ` [Qemu-devel] " Stefan Weil
2010-04-19 19:55 ` Blue Swirl
2010-04-19 20:33 ` Artyom Tarasenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=q2zfb8d4f71004191333w45186ecq155452531af07565@mail.gmail.com \
--to=atar4qemu@googlemail.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).