From: Stuart Anderson <anderson@netsweng.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] RFC: [0/11] EFAULT patch
Date: Wed, 19 Sep 2007 07:30:49 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0709190725590.20150@trantor.stuart.netsweng.com> (raw)
In-Reply-To: <1190167518.14938.348.camel@rapid>
On Wed, 19 Sep 2007, J. Mayer wrote:
> The idea is great but there seem to be a problem in those patches:
> you directly cast syscall arguments, which are (or should be)
> target_ulong to pointers in the host environment. You should to use the
> g2h / h2g macros to get the pointer in the host memory from the offset
> in the target address space.
I was explicitly told to _not_ use these in this code.
> Offset in the target address space can not
> be assumed to be the same size as an address in the host address space,
And in fact, they definitely are not the same in certain cobinations.
> thus can never be casted directly to host pointer.
At some point, we have to convert things from target_long to a host
pointer. If we can agree on what that right mechanism it to do this, I'd
be glad to use it. So far, everything I've seen involved some form of
type casting.
> This used to be handled by the lock_user functions and should be handled
> in your patch too...
It was handled by g2h() which was just a typecast hidden behind the
macro.
Stuart
Stuart R. Anderson anderson@netsweng.com
Network & Software Engineering http://www.netsweng.com/
1024D/37A79149: 0791 D3B8 9A4C 2CDC A31F
BD03 0A62 E534 37A7 9149
next prev parent reply other threads:[~2007-09-19 11:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 0:59 [Qemu-devel] RFC: [0/11] EFAULT patch Stuart Anderson
2007-09-19 2:05 ` J. Mayer
2007-09-19 11:30 ` Stuart Anderson [this message]
2007-09-19 15:22 ` Paul Brook
2007-09-19 19:00 ` Stuart Anderson
2007-09-19 19:26 ` J. Mayer
2007-09-19 20:00 ` Paul Brook
2007-09-19 20:44 ` Stuart Anderson
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=Pine.LNX.4.64.0709190725590.20150@trantor.stuart.netsweng.com \
--to=anderson@netsweng.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).