From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] checking if linux-user address is mapped (sparc)
Date: Wed, 3 Sep 2008 19:08:26 +0300 [thread overview]
Message-ID: <f43fc5580809030908n1414d8a9rcb4e5a037aecde9c@mail.gmail.com> (raw)
In-Reply-To: <20080902165557.X88242@stanley.csl.cornell.edu>
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
On 9/3/08, Vince Weaver <vince@csl.cornell.edu> wrote:
> 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.
Could you test this patch?
[-- Attachment #2: no_fault_accesses.diff --]
[-- Type: plain/text, Size: 2814 bytes --]
next prev parent reply other threads:[~2008-09-03 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 21:01 [Qemu-devel] checking if linux-user address is mapped (sparc) Vince Weaver
2008-09-03 16:08 ` Blue Swirl [this message]
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=f43fc5580809030908n1414d8a9rcb4e5a037aecde9c@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).