From: Vince Weaver <vince@csl.cornell.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] checking if linux-user address is mapped (sparc)
Date: Tue, 2 Sep 2008 17:01:49 -0400 (EDT) [thread overview]
Message-ID: <20080902165557.X88242@stanley.csl.cornell.edu> (raw)
Hello
so now I'm trying to get the vpr spec2k benchmarks going under
sparc32plus-linux-user
In an optimized memory scanning routine the code is doing:
ldxa [ %o0 ] #ASI_PNF, %o3
Which is a load from the "no fault" address space.
What this means is that even if you are loading from an invalid address,
no fault should occur.
qemu of course segfaults when the address is invalid.
Is there some way to check in linux-user if a virtual memory address is
mapped? That way it could be checked before the ldl_raw() is run?
hopefully I am not misunderstanding the bug here.
Vince
next reply other threads:[~2008-09-02 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 21:01 Vince Weaver [this message]
2008-09-03 16:08 ` [Qemu-devel] checking if linux-user address is mapped (sparc) Blue Swirl
2008-09-03 17:16 ` Vince Weaver
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=20080902165557.X88242@stanley.csl.cornell.edu \
--to=vince@csl.cornell.edu \
--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).