From: Dave Airlie <airlied@redhat.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Keith Packard <keithp@keithp.com>, Eric Anholt <eric@anholt.net>,
Nick Piggin <npiggin@suse.de>, Matt Mackall <mpm@selenic.com>,
David Howells <dhowells@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Export tiny shmem_file_setup for DRM-GEM
Date: Tue, 21 Oct 2008 06:20:21 +1000 [thread overview]
Message-ID: <1224534021.3656.2.camel@optimus> (raw)
In-Reply-To: <Pine.LNX.4.64.0810191242220.22825@blonde.site>
On Sun, 2008-10-19 at 12:52 +0100, Hugh Dickins wrote:
> We're trying to keep the !CONFIG_SHMEM tiny-shmem.c (using ramfs without
> swap) in synch with CONFIG_SHMEM shmem.c (and mpm is preparing patches
> to combine them). I was glad to see EXPORT_SYMBOL_GPL(shmem_file_setup)
> go into shmem.c, but why not support DRM-GEM when !CONFIG_SHMEM too?
> But caution says still depend on MMU, since !CONFIG_MMU is.. different.
>
> Signed-off-by: Hugh Dickins <hugh@veritas.com>
Acked-by: Dave Airlie <airlied@redhat.com>
> ---
> I should admit that I've not actually tested this patch,
> but can't imagine why it would be a problem: if you gobble
> up too much RAM, well, that's just life with tiny-shmem.
>
> I did promise a patch to make read_mapping_page() return -EINVAL instead
> of oopsing when the underlying filesystem doesn't support it. But that
> was when people were trying to persuade GEM to map files on whatever fs:
> I can't now see the point of such a patch while you're known to be on
> tmpfs or ramfs, and intending later to use a new interface from Nick.
>
> drivers/gpu/drm/Kconfig | 2 +-
> mm/tiny-shmem.c | 1 +
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> --- a/drivers/gpu/drm/Kconfig
> +++ b/drivers/gpu/drm/Kconfig
> @@ -6,7 +6,7 @@
> #
> menuconfig DRM
> tristate "Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)"
> - depends on (AGP || AGP=n) && PCI && !EMULATED_CMPXCHG && SHMEM
> + depends on (AGP || AGP=n) && PCI && !EMULATED_CMPXCHG && MMU
> help
> Kernel-level support for the Direct Rendering Infrastructure (DRI)
> introduced in XFree86 4.0. If you say Y here, you need to select
> --- a/mm/tiny-shmem.c
> +++ b/mm/tiny-shmem.c
> @@ -95,6 +95,7 @@ put_dentry:
> put_memory:
> return ERR_PTR(error);
> }
> +EXPORT_SYMBOL_GPL(shmem_file_setup);
>
> /**
> * shmem_zero_setup - setup a shared anonymous mapping
next prev parent reply other threads:[~2008-10-20 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 11:52 [PATCH] Export tiny shmem_file_setup for DRM-GEM Hugh Dickins
2008-10-20 18:02 ` Matt Mackall
2008-10-20 18:47 ` Hugh Dickins
2008-10-20 19:38 ` Matt Mackall
2008-10-20 20:20 ` Dave Airlie [this message]
2008-10-20 23:04 ` Hugh Dickins
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=1224534021.3656.2.camel@optimus \
--to=airlied@redhat.com \
--cc=dhowells@redhat.com \
--cc=eric@anholt.net \
--cc=hugh@veritas.com \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=npiggin@suse.de \
/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.