From: Andrew Morton <akpm@linux-foundation.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: extend prefault helpers to fault in more than PAGE_SIZE
Date: Thu, 1 Mar 2012 12:15:57 -0800 [thread overview]
Message-ID: <20120301121557.0e0fd728.akpm@linux-foundation.org> (raw)
In-Reply-To: <1330629779-1449-1-git-send-email-daniel.vetter@ffwll.ch>
On Thu, 1 Mar 2012 20:22:59 +0100
Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> drm/i915 wants to read/write more than one page in its fastpath
> and hence needs to prefault more than PAGE_SIZE bytes.
>
> Add new functions in filemap.h to make that possible.
>
> Also kill a copy&pasted spurious space in both functions while at it.
>
>
> ...
>
> +/* Multipage variants of the above prefault helpers, useful if more than
> + * PAGE_SIZE of date needs to be prefaulted. These are separate from the above
> + * functions (which only handle up to PAGE_SIZE) to avoid clobbering the
> + * filemap.c hotpaths. */
Like this please:
/*
* Multipage variants of the above prefault helpers, useful if more than
* PAGE_SIZE of date needs to be prefaulted. These are separate from the above
* functions (which only handle up to PAGE_SIZE) to avoid clobbering the
* filemap.c hotpaths.
*/
and s/date/data/
> +static inline int fault_in_multipages_writeable(char __user *uaddr, int size)
> +{
> + int ret;
> + const char __user *end = uaddr + size - 1;
> +
> + if (unlikely(size == 0))
> + return 0;
> +
> + /*
> + * Writing zeroes into userspace here is OK, because we know that if
> + * the zero gets there, we'll be overwriting it.
> + */
Yeah, like that.
> + while (uaddr <= end) {
> + ret = __put_user(0, uaddr);
> + if (ret != 0)
> + return ret;
> + uaddr += PAGE_SIZE;
> + }
> +
> + /* Check whether the range spilled into the next page. */
> + if (((unsigned long)uaddr & PAGE_MASK) ==
> + ((unsigned long)end & PAGE_MASK))
> + ret = __put_user(0, end);
> +
> + return ret;
> +}
> +
> +static inline int fault_in_multipages_readable(const char __user *uaddr,
> + int size)
> +{
> + volatile char c;
> + int ret;
> + const char __user *end = uaddr + size - 1;
> +
> + if (unlikely(size == 0))
> + return 0;
> +
> + while (uaddr <= end) {
> + ret = __get_user(c, uaddr);
> + if (ret != 0)
> + return ret;
> + uaddr += PAGE_SIZE;
> + }
> +
> + /* Check whether the range spilled into the next page. */
> + if (((unsigned long)uaddr & PAGE_MASK) ==
> + ((unsigned long)end & PAGE_MASK)) {
> + ret = __get_user(c, end);
> + (void)c;
> + }
> +
> + return ret;
> +}
Please merge it via the DRI tree.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: extend prefault helpers to fault in more than PAGE_SIZE
Date: Thu, 1 Mar 2012 12:15:57 -0800 [thread overview]
Message-ID: <20120301121557.0e0fd728.akpm@linux-foundation.org> (raw)
In-Reply-To: <1330629779-1449-1-git-send-email-daniel.vetter@ffwll.ch>
On Thu, 1 Mar 2012 20:22:59 +0100
Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> drm/i915 wants to read/write more than one page in its fastpath
> and hence needs to prefault more than PAGE_SIZE bytes.
>
> Add new functions in filemap.h to make that possible.
>
> Also kill a copy&pasted spurious space in both functions while at it.
>
>
> ...
>
> +/* Multipage variants of the above prefault helpers, useful if more than
> + * PAGE_SIZE of date needs to be prefaulted. These are separate from the above
> + * functions (which only handle up to PAGE_SIZE) to avoid clobbering the
> + * filemap.c hotpaths. */
Like this please:
/*
* Multipage variants of the above prefault helpers, useful if more than
* PAGE_SIZE of date needs to be prefaulted. These are separate from the above
* functions (which only handle up to PAGE_SIZE) to avoid clobbering the
* filemap.c hotpaths.
*/
and s/date/data/
> +static inline int fault_in_multipages_writeable(char __user *uaddr, int size)
> +{
> + int ret;
> + const char __user *end = uaddr + size - 1;
> +
> + if (unlikely(size == 0))
> + return 0;
> +
> + /*
> + * Writing zeroes into userspace here is OK, because we know that if
> + * the zero gets there, we'll be overwriting it.
> + */
Yeah, like that.
> + while (uaddr <= end) {
> + ret = __put_user(0, uaddr);
> + if (ret != 0)
> + return ret;
> + uaddr += PAGE_SIZE;
> + }
> +
> + /* Check whether the range spilled into the next page. */
> + if (((unsigned long)uaddr & PAGE_MASK) ==
> + ((unsigned long)end & PAGE_MASK))
> + ret = __put_user(0, end);
> +
> + return ret;
> +}
> +
> +static inline int fault_in_multipages_readable(const char __user *uaddr,
> + int size)
> +{
> + volatile char c;
> + int ret;
> + const char __user *end = uaddr + size - 1;
> +
> + if (unlikely(size == 0))
> + return 0;
> +
> + while (uaddr <= end) {
> + ret = __get_user(c, uaddr);
> + if (ret != 0)
> + return ret;
> + uaddr += PAGE_SIZE;
> + }
> +
> + /* Check whether the range spilled into the next page. */
> + if (((unsigned long)uaddr & PAGE_MASK) ==
> + ((unsigned long)end & PAGE_MASK)) {
> + ret = __get_user(c, end);
> + (void)c;
> + }
> +
> + return ret;
> +}
Please merge it via the DRI tree.
next prev parent reply other threads:[~2012-03-01 20:15 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 12:01 [PATCH] extend prefault helpers to fault in more than PAGE_SIZE Daniel Vetter
2012-02-16 12:01 ` Daniel Vetter
2012-02-16 12:01 ` Daniel Vetter
2012-02-16 12:01 ` [PATCH] mm: " Daniel Vetter
2012-02-16 12:01 ` Daniel Vetter
2012-02-16 13:32 ` Hillf Danton
2012-02-16 13:32 ` Hillf Danton
2012-02-16 15:14 ` Daniel Vetter
2012-02-16 15:14 ` Daniel Vetter
2012-02-16 15:14 ` Daniel Vetter
2012-02-17 13:06 ` Hillf Danton
2012-02-17 13:06 ` Hillf Danton
2012-02-23 22:36 ` Andrew Morton
2012-02-23 22:36 ` Andrew Morton
2012-02-24 13:34 ` Daniel Vetter
2012-02-24 13:34 ` Daniel Vetter
2012-02-24 20:40 ` Andrew Morton
2012-02-24 20:40 ` Andrew Morton
2012-02-29 14:03 ` Daniel Vetter
2012-02-29 14:03 ` Daniel Vetter
2012-02-29 23:01 ` Andrew Morton
2012-02-29 23:01 ` Andrew Morton
2012-02-29 23:14 ` Daniel Vetter
2012-02-29 23:14 ` Daniel Vetter
2012-02-29 23:32 ` Andrew Morton
2012-02-29 23:32 ` Andrew Morton
2012-03-01 19:22 ` Daniel Vetter
2012-03-01 19:22 ` Daniel Vetter
2012-03-01 20:15 ` Andrew Morton [this message]
2012-03-01 20:15 ` Andrew Morton
2012-03-27 11:37 ` Daniel Vetter
2012-03-27 11:37 ` Daniel Vetter
2012-04-13 19:12 ` Geert Uytterhoeven
2012-04-13 19:12 ` Geert Uytterhoeven
2012-04-14 16:03 ` [PATCH] mm: fixup compilation error due to an asm write through a const pointer Daniel Vetter
2012-04-14 16:03 ` Daniel Vetter
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=20120301121557.0e0fd728.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.