From: Artyom Tarasenko <atar4qemu@googlemail.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: sparc32 do_unassigned_access overhaul v2
Date: Mon, 18 Jan 2010 17:17:03 +0100 [thread overview]
Message-ID: <fb8d4f71001180817w1273ef2dyf6f39b3966109ef9@mail.gmail.com> (raw)
In-Reply-To: <f43fc5581001151334o745e56fajafcff5066c220882@mail.gmail.com>
Btw, what is the following hack for in do_unassigned_access?
saved_env = env;
env = cpu_single_env;
//...
env = saved_env;
I wonder whether I modify the correct env here:
env = saved_env;
+ /* flush neverland mappings created during no-fault mode,
+ so the sequential MMU faults report proper fault types */
+ if (env->mmuregs[0] & MMU_NF) {
+ tlb_flush(env, 1);
+ }
--
Regards,
Artyom Tarasenko
solaris/sparc under qemu blog: http://tyom.blogspot.com/
next prev parent reply other threads:[~2010-01-18 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 21:28 [Qemu-devel] sparc32 do_unassigned_access overhaul v2 Artyom Tarasenko
2010-01-15 21:34 ` [Qemu-devel] " Blue Swirl
2010-01-18 16:17 ` Artyom Tarasenko [this message]
2010-01-18 17:38 ` 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=fb8d4f71001180817w1273ef2dyf6f39b3966109ef9@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).