From: Artyom Tarasenko <atar4qemu@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>, Blue Swirl <blauwirbel@gmail.com>
Subject: [Qemu-devel] Re: phys_page_find bug?
Date: Mon, 8 Nov 2010 19:55:43 +0100 [thread overview]
Message-ID: <AANLkTikVYebUGUfMw3J5NP3BYWCYkGM0VS-++ByLbKWu@mail.gmail.com> (raw)
In-Reply-To: <q2pfb8d4f71005070926y8d6f9208y9a6b5eb6a70b77cb@mail.gmail.com>
On Fri, May 7, 2010 at 6:26 PM, Artyom Tarasenko
<atar4qemu@googlemail.com> wrote:
> phys_page_find (exec.c) returns sometimes a page for addresses where
> nothing is connected.
>
> One example, done with qemu-system-sparc -M SS-20
>
> ok f13ffff0 2f spacec@ .
>
> // The address translates correctly, in cpu_physical_memory_rw
> // addr== 0xff13ffff0 (where nothing is connected)
> // but then phys_page_find returns a nonzero and produces
>
> Unassigned mem read access of 1 byte to 0000000ff15ffff0 from xxxxx
>
> (note the "5" in the line above where "3" is expected)
>
> I wonder if this is only true for non-wired addresses, or whether
> phys_page_find can also
> find wrong pages for the addresses where something is connected?
>
> Or is my assumption is wrong and phys_page_find can return a page for
> not-connected
> addresses and the bug is actually in cpu_physical_memory_rw ?
>
> Is the qemu algorithm of working with the physical address space
> described somewhere?
I tried to switch devices off and found that the bug is triggered by
registering escc.
It's harder to debug without escc, so I can't tell whether something
else is causing
the problem too.
Is escc addressing somehow special?
>Is the qemu algorithm of working with the physical address space described somewhere?
I guess no one knows it anymore, since no-one cared to answer within a
half year :-/.
--
Regards,
Artyom Tarasenko
solaris/sparc under qemu blog: http://tyom.blogspot.com/
next prev parent reply other threads:[~2010-11-08 18:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 16:26 [Qemu-devel] phys_page_find bug? Artyom Tarasenko
2010-05-20 20:00 ` [Qemu-devel] " Artyom Tarasenko
2010-11-08 18:55 ` Artyom Tarasenko [this message]
2010-11-09 17:53 ` Blue Swirl
2011-01-10 3:57 ` Bob Breuer
2011-01-10 21:39 ` Blue Swirl
2011-01-11 6:49 ` Bob Breuer
2011-01-11 9:22 ` Artyom Tarasenko
2011-01-11 15:46 ` Bob Breuer
2011-02-04 11:44 ` 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=AANLkTikVYebUGUfMw3J5NP3BYWCYkGM0VS-++ByLbKWu@mail.gmail.com \
--to=atar4qemu@gmail.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).