From: Paul Brook <paul@codesourcery.com>
To: thayne@c2.net
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target_posix_types.h
Date: Wed, 14 Nov 2007 21:37:46 +0000 [thread overview]
Message-ID: <200711142137.48495.paul@codesourcery.com> (raw)
In-Reply-To: <1195075167.918.103.camel@phantasm.home.enterpriseandprosperity.com>
> time_t is only one example. There are similar problems with the
> handling of struct target_iovec. There are still other places with
> similar problems.
>
> Yes, special casing can work. There's the possible problem of value
> truncation when moving between 32 and 64 bits.
My point is that I expect there the be sufficiently many special cases that
you can't simply rely on get_user() doing the right thing, even if you
have "proper" types everywhere.
It's also unclear whether sign extensions should depend on host or guest
properties.
Paul
next prev parent reply other threads:[~2007-11-14 21:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 15:59 [Qemu-devel] [PATCH] target_posix_types.h Thayne Harbaugh
2007-11-14 16:03 ` [Qemu-devel] Re: [PATCH] tget/tput deprecation Thayne Harbaugh
2007-11-14 16:08 ` Thayne Harbaugh
2007-11-14 18:21 ` Thayne Harbaugh
2007-11-14 19:02 ` Thayne Harbaugh
2007-11-16 4:16 ` Thayne Harbaugh
2007-11-14 16:25 ` [Qemu-devel] [PATCH] target_posix_types.h Jocelyn Mayer
2007-11-14 17:36 ` Thiemo Seufer
2007-11-14 17:54 ` Jocelyn Mayer
2007-11-14 18:20 ` Thayne Harbaugh
2007-11-14 18:32 ` Fabrice Bellard
2007-11-14 18:43 ` Thayne Harbaugh
2007-11-14 19:14 ` Fabrice Bellard
2007-11-14 19:53 ` Thayne Harbaugh
2007-11-14 20:39 ` Paul Brook
2007-11-14 21:06 ` Warner Losh
2007-11-14 21:25 ` Thayne Harbaugh
2007-11-14 21:19 ` Thayne Harbaugh
2007-11-14 21:37 ` Paul Brook [this message]
2007-11-14 19:56 ` Thayne Harbaugh
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=200711142137.48495.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=thayne@c2.net \
/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).