From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] sparc32 remote debugger mem access problems with 0.9.1
Date: Thu, 14 Feb 2008 19:43:13 +0200 [thread overview]
Message-ID: <f43fc5580802140943r32db3541g90669de20b433a73@mail.gmail.com> (raw)
In-Reply-To: <OFE1FB2389.F967B501-ONC12573EF.002CD0C9-412573EF.002DF6C9@gom.com>
On 2/14/08, M.Stein@gom.com <M.Stein@gom.com> wrote:
> Hello,
>
> recently I have updated my qemu from 0.9.0 to 0.9.1 and had problems
> with the remote debugger memory access. Especially the command
>
> x /10i 0x4000
>
> doesn't work, even if the PC is 0x4000.
>
> I have tracked down the problem till target-sparc/translate.c, where the
> following calls are done:
>
> if (get_physical_address(env, &phys_addr, &prot, &access_index, addr,
> 2, 0) != 0)
> if (get_physical_address(env, &phys_addr, &prot, &access_index,
> addr, 0, 0) != 0)
> return -1;
>
> In 0.9.0 the last arg to get_physical_address was 'is_user', now it is
> 'mmu_idx'. is_user
> is now evaluated in target-sparc/helper.c:get_physical_adress by
>
> is_user = mmu_idx == MMU_USER_IDX;
>
> So if 'mmu_idx' ist still 0 (and MMU_USER_IDX is also 0) the resulting
> 'is_user' is TRUE
> and the later
>
> error_code = access_table[*access_index][access_perms];
> if (error_code && !((env->mmuregs[0] & MMU_NF) && is_user))
> return error_code;
>
> always fails with access_index 0/2 and access_perms 7.
>
> I have changed the last arg of get_physical_address to 1 and all works as
> expected.
Thank you for the analysis! I'll commit the change.
prev parent reply other threads:[~2008-02-14 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 8:22 [Qemu-devel] sparc32 remote debugger mem access problems with 0.9.1 M.Stein
2008-02-14 17:43 ` Blue Swirl [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=f43fc5580802140943r32db3541g90669de20b433a73@mail.gmail.com \
--to=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).