From: Artyom Tarasenko <atar4qemu@gmail.com>
To: Blue Swirl <blauwirbel@gmail.com>, Avi Kivity <avi@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Leon3 is broken since 6281f7d11
Date: Wed, 25 Jan 2012 12:06:06 +0100 [thread overview]
Message-ID: <CACXAS8CVUc-RL5Sgkhw6EQWtf=BCjqAaWC6phgXMg1ML+ZRm0g@mail.gmail.com> (raw)
In-Reply-To: <CACXAS8CWQjU0kDi1AWoSk4speaZzy=kOH4VvvezXrQ9jLMS=wg@mail.gmail.com>
Leon3 machine is broken in the current git master.
Bisect shows the following:
6281f7d11fa6bfb6da3926359fbe70684e582cb1 is the first bad commit
commit 6281f7d11fa6bfb6da3926359fbe70684e582cb1
Author: Avi Kivity <avi@redhat.com>
Date: Mon Nov 14 13:10:13 2011 +0200
grlib_apbuart: convert to memory API
Signed-off-by: Avi Kivity <avi@redhat.com>
I've asked the author's permission to publish the test program. Until
he responds here is some preliminary analysis. Before the memory API
running the test program (with unassigned access debugging turned on)
looked like this:
$ sparc-softmmu/qemu-system-sparc -M leon3_generic -kernel ravenscar-test
Unassigned mem read access of 4 bytes to 0000000000000108 from 400080d0
Unassigned mem write access of 1 byte to 0000000040032af5 asi 0x01 from 40003c4c
Unassigned mem read access of 2 bytes to 0000000000000212 from 40006ca8
...
Currently it looks like this:
$ sparc-softmmu/qemu-system-sparc -M leon3_generic -kernel ravenscar-test
Unassigned mem write access of 1 byte to 0000000040032af5 asi 0x01 from
<hang>
It looks that qemu produces less 'unassigned mem read accesses' than before.
Unfortunately, there seems to be another bug in the logging, because I
don't see what could have triggered the unassigned access at 400080d0,
but there is a good candidate at 400080d8 though:
IN: system__bb__peripherals__initialize_uart
0x400080d0: sethi %hi(0x80000000), %g1
0x400080d4: or %g1, 0x108, %g1 ! 0x80000108
0x400080d8: ld [ %g1 ], %g1
0x400080dc: btst 1, %g1
0x400080e0: bne 0x400081a4
0x400080e4: btst 2, %g1
Artyom
--
Regards,
Artyom Tarasenko
solaris/sparc under qemu blog: http://tyom.blogspot.com/search/label/qemu
next parent reply other threads:[~2012-01-25 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACXAS8CWQjU0kDi1AWoSk4speaZzy=kOH4VvvezXrQ9jLMS=wg@mail.gmail.com>
2012-01-25 11:06 ` Artyom Tarasenko [this message]
2012-01-25 20:11 ` [Qemu-devel] Leon3 is broken since 6281f7d11 Artyom Tarasenko
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='CACXAS8CVUc-RL5Sgkhw6EQWtf=BCjqAaWC6phgXMg1ML+ZRm0g@mail.gmail.com' \
--to=atar4qemu@gmail.com \
--cc=avi@redhat.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).