From: Artyom Tarasenko <atar4qemu@gmail.com>
To: "Igor V. Kovalenko" <igor.v.kovalenko@gmail.com>,
Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 4/5] sparc64: fix mmu context at trap levels above zero
Date: Mon, 4 Apr 2011 19:25:44 +0200 [thread overview]
Message-ID: <BANLkTim90_w+efqZBnfZwJZqao3ATw2-OQ@mail.gmail.com> (raw)
In-Reply-To: <20100522105234.18257.53650.stgit@skyserv>
On Sat, May 22, 2010 at 12:52 PM, Igor V. Kovalenko
<igor.v.kovalenko@gmail.com> wrote:
> --- a/target-sparc/helper.c
> +++ b/target-sparc/helper.c
> @@ -572,6 +572,23 @@ static int get_physical_address(CPUState *env, target_phys_addr_t *physical,
> /* ??? We treat everything as a small page, then explicitly flush
> everything when an entry is evicted. */
> *page_size = TARGET_PAGE_SIZE;
> +
> +#if defined (DEBUG_MMU)
> + /* safety net to catch wrong softmmu index use from dynamic code */
What does "wrong softmmu index" mean? Is it an error or an indication
that something is not implemented?
I'm hitting this net with the following message:
get_physical_address DATA tl=1 mmu_idx=2 primary context=0 secondary
context=0 address=fffb5f40
> + if (env->tl > 0 && mmu_idx != MMU_NUCLEUS_IDX) {
> + DPRINTF_MMU("get_physical_address %s tl=%d mmu_idx=%d"
> + " primary context=%" PRIx64
> + " secondary context=%" PRIx64
> + " address=%" PRIx64
> + "\n",
> + (rw == 2 ? "CODE" : "DATA"),
> + env->tl, mmu_idx,
> + env->dmmu.mmu_primary_context,
> + env->dmmu.mmu_secondary_context,
> + address);
> + }
> +#endif
Artyom
--
Regards,
Artyom Tarasenko
solaris/sparc under qemu blog: http://tyom.blogspot.com/
next prev parent reply other threads:[~2011-04-04 17:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 10:52 [Qemu-devel] [PATCH 0/5] allow HelenOS to start userspace tasks under qemu-system-sparc64 Igor V. Kovalenko
2010-05-22 10:52 ` [Qemu-devel] [PATCH 1/5] sparc64: generate data access exception on RW violation Igor V. Kovalenko
2010-05-22 10:52 ` [Qemu-devel] [PATCH 2/5] sparc64: fix pstate privilege bits Igor V. Kovalenko
2010-05-22 10:52 ` [Qemu-devel] [PATCH 3/5] sparc64: fix dump_mmu to look for global bit in tte value instead of tag Igor V. Kovalenko
2010-05-22 10:52 ` [Qemu-devel] [PATCH 4/5] sparc64: fix mmu context at trap levels above zero Igor V. Kovalenko
2011-04-04 17:25 ` Artyom Tarasenko [this message]
2011-04-04 18:37 ` Blue Swirl
2011-04-04 19:12 ` Igor Kovalenko
2010-05-22 10:52 ` [Qemu-devel] [PATCH 5/5] sparc64: flush translations on mmu context change Igor V. Kovalenko
2010-05-22 13:16 ` [Qemu-devel] [PATCH 0/5] allow HelenOS to start userspace tasks under qemu-system-sparc64 Blue Swirl
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=BANLkTim90_w+efqZBnfZwJZqao3ATw2-OQ@mail.gmail.com \
--to=atar4qemu@gmail.com \
--cc=blauwirbel@gmail.com \
--cc=igor.v.kovalenko@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).