From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Rob Clark <robdclark@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [RFCv1 12/12] ARM: add get_user() support for 8 byte types
Date: Sun, 6 Oct 2013 09:53:54 +0100 [thread overview]
Message-ID: <20131006085354.GC12758@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1381020350-1125-13-git-send-email-robdclark@gmail.com>
On Sat, Oct 05, 2013 at 08:45:50PM -0400, Rob Clark wrote:
> A new atomic modeset/pageflip ioctl being developed in DRM requires
> get_user() to work for 64bit types (in addition to just put_user()).
>
> v1: original
> v2: pass correct size to check_uaccess, and better handling of narrowing
> double word read with __get_user_xb() (Russell King's suggestion)
I thought we had decided not to support this for 32-bit because x86_32
had problems here as well:
#ifdef CONFIG_X86_32
#define __get_user_asm_u64(x, ptr, retval, errret) (x) = __get_user_bad()
#define __get_user_asm_ex_u64(x, ptr) (x) = __get_user_bad()
#else
#define __get_user_asm_u64(x, ptr, retval, errret) \
__get_user_asm(x, ptr, retval, "q", "", "=r", errret)
#define __get_user_asm_ex_u64(x, ptr) \
__get_user_asm_ex(x, ptr, "q", "", "=r")
#endif
next prev parent reply other threads:[~2013-10-06 8:54 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 0:45 [RFCv1 00/12] Atomic/nuclear modeset/pageflip Rob Clark
2013-10-06 0:45 ` [RFCv1 01/12] drm: add atomic fxns Rob Clark
2013-10-06 0:45 ` [RFCv1 02/12] drm: add object property type Rob Clark
2013-10-07 13:43 ` Ville Syrjälä
2013-10-07 14:44 ` Rob Clark
2013-10-06 0:45 ` [RFCv1 03/12] drm: add DRM_MODE_PROP_DYNAMIC property flag Rob Clark
2013-10-07 13:46 ` Ville Syrjälä
2013-10-07 14:46 ` Rob Clark
2013-10-06 0:45 ` [RFCv1 04/12] drm: add DRM_MODE_PROP_SIGNED " Rob Clark
2013-10-07 14:46 ` Matt Plumtree
2013-10-06 0:45 ` [RFCv1 05/12] drm: helpers to find mode objects (BEFORE drm: split property values out) Rob Clark
2013-10-06 0:48 ` Rob Clark
2013-10-06 0:45 ` [RFCv1 06/12] drm: split propvals out and blob property support Rob Clark
2013-10-06 0:45 ` [RFCv1 07/12] drm: Allow drm_mode_object_find() to look up an object of any type Rob Clark
2013-10-06 0:45 ` [RFCv1 08/12] drm: Refactor object property check code Rob Clark
2013-10-07 13:47 ` Ville Syrjälä
2013-10-06 0:45 ` [RFCv1 09/12] drm: convert plane to properties/state Rob Clark
2013-10-06 0:45 ` [RFCv1 10/12] drm: convert crtc " Rob Clark
2013-10-07 13:39 ` Ville Syrjälä
2013-10-07 14:03 ` Rob Clark
2013-10-07 14:19 ` Ville Syrjälä
2013-10-07 14:29 ` Rob Clark
2013-10-07 17:51 ` Daniel Vetter
2013-10-06 0:45 ` [RFCv1 11/12] drm: Atomic modeset ioctl Rob Clark
2013-10-07 13:28 ` Ville Syrjälä
2013-10-07 13:55 ` Rob Clark
2013-10-07 14:18 ` Ville Syrjälä
2013-10-07 14:39 ` Rob Clark
2013-10-07 15:05 ` Ville Syrjälä
2013-10-07 15:20 ` Rob Clark
2013-10-07 17:56 ` Daniel Vetter
2013-10-07 18:49 ` Rob Clark
2013-10-08 18:35 ` Matt Roper
2013-10-08 18:46 ` Rob Clark
2013-10-06 0:45 ` [RFCv1 12/12] ARM: add get_user() support for 8 byte types Rob Clark
2013-10-06 8:53 ` Russell King - ARM Linux [this message]
2013-10-06 14:09 ` Rob Clark
2013-10-06 15:56 ` Russell King - ARM Linux
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=20131006085354.GC12758@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=robdclark@gmail.com \
/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).