From: Johannes Weiner <hannes@cmpxchg.org>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-media@vger.kernel.org, hverkuil@xs4all.nl,
linux-mm@kvack.org, lethal@linux-sh.org
Subject: Re: [PATCH] videobuf-dma-contig: zero copy USERPTR support V2
Date: Fri, 1 May 2009 20:14:49 +0200 [thread overview]
Message-ID: <20090501181449.GA8912@cmpxchg.org> (raw)
In-Reply-To: <aec7e5c30904302026q42ecbd57m6e88c937bbd262bb@mail.gmail.com>
On Fri, May 01, 2009 at 12:26:38PM +0900, Magnus Damm wrote:
> On Tue, Apr 28, 2009 at 6:01 PM, Magnus Damm <magnus.damm@gmail.com> wrote:
> > This is V2 of the V4L2 videobuf-dma-contig USERPTR zero copy patch.
>
> I guess the V4L2 specific bits are pretty simple.
>
> As for the minor mm modifications below,
>
> > --- 0001/mm/memory.c
> > +++ work/mm/memory.c 2009-04-28 14:56:43.000000000 +0900
> > @@ -3009,7 +3009,6 @@ int in_gate_area_no_task(unsigned long a
> >
> > #endif /* __HAVE_ARCH_GATE_AREA */
> >
> > -#ifdef CONFIG_HAVE_IOREMAP_PROT
> > int follow_phys(struct vm_area_struct *vma,
> > unsigned long address, unsigned int flags,
> > unsigned long *prot, resource_size_t *phys)
>
> Is it ok with the memory management guys to always build follow_phys()?
AFAICS, pte_pgprot is only defined on three architectures that have
the config symbol above set. It shouldn't compile on the others.
I have a patch that factors out follow_pte and builds follow_pfn and
follow_phys on top of that. I can send it monday, no access to it
from here right now.
Then we can keep follow_phys private to this configuration.
Hannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Weiner <hannes@cmpxchg.org>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-media@vger.kernel.org, hverkuil@xs4all.nl,
linux-mm@kvack.org, lethal@linux-sh.org
Subject: Re: [PATCH] videobuf-dma-contig: zero copy USERPTR support V2
Date: Fri, 1 May 2009 20:14:49 +0200 [thread overview]
Message-ID: <20090501181449.GA8912@cmpxchg.org> (raw)
In-Reply-To: <aec7e5c30904302026q42ecbd57m6e88c937bbd262bb@mail.gmail.com>
On Fri, May 01, 2009 at 12:26:38PM +0900, Magnus Damm wrote:
> On Tue, Apr 28, 2009 at 6:01 PM, Magnus Damm <magnus.damm@gmail.com> wrote:
> > This is V2 of the V4L2 videobuf-dma-contig USERPTR zero copy patch.
>
> I guess the V4L2 specific bits are pretty simple.
>
> As for the minor mm modifications below,
>
> > --- 0001/mm/memory.c
> > +++ work/mm/memory.c 2009-04-28 14:56:43.000000000 +0900
> > @@ -3009,7 +3009,6 @@ int in_gate_area_no_task(unsigned long a
> >
> > #endif /* __HAVE_ARCH_GATE_AREA */
> >
> > -#ifdef CONFIG_HAVE_IOREMAP_PROT
> > int follow_phys(struct vm_area_struct *vma,
> > unsigned long address, unsigned int flags,
> > unsigned long *prot, resource_size_t *phys)
>
> Is it ok with the memory management guys to always build follow_phys()?
AFAICS, pte_pgprot is only defined on three architectures that have
the config symbol above set. It shouldn't compile on the others.
I have a patch that factors out follow_pte and builds follow_pfn and
follow_phys on top of that. I can send it monday, no access to it
from here right now.
Then we can keep follow_phys private to this configuration.
Hannes
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-05-01 18:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 9:01 [PATCH] videobuf-dma-contig: zero copy USERPTR support V2 Magnus Damm
2009-04-28 9:01 ` Magnus Damm
2009-05-01 3:26 ` Magnus Damm
2009-05-01 3:26 ` Magnus Damm
2009-05-01 18:14 ` Johannes Weiner [this message]
2009-05-01 18:14 ` Johannes Weiner
2009-05-04 9:54 ` [patch 1/3] mm: introduce follow_pte() Johannes Weiner
2009-05-04 9:54 ` Johannes Weiner
2009-05-05 19:24 ` Andrew Morton
2009-05-05 19:24 ` Andrew Morton
2009-05-05 20:38 ` Johannes Weiner
2009-05-05 20:38 ` Johannes Weiner
2009-05-05 21:05 ` Andrew Morton
2009-05-05 21:05 ` Andrew Morton
2009-05-05 21:21 ` Johannes Weiner
2009-05-05 21:21 ` Johannes Weiner
2009-05-08 8:51 ` Magnus Damm
2009-05-08 8:51 ` Magnus Damm
2009-05-04 9:54 ` [patch 2/3] mm: use generic follow_pte() in follow_phys() Johannes Weiner
2009-05-04 9:54 ` Johannes Weiner
2009-05-04 10:08 ` Johannes Weiner
2009-05-04 10:08 ` Johannes Weiner
2009-05-04 9:54 ` [patch 3/3] mm: introduce follow_pfn() Johannes Weiner
2009-05-04 9:54 ` Johannes Weiner
2009-05-04 11:08 ` Christoph Hellwig
2009-05-04 11:08 ` Christoph Hellwig
2009-05-04 13:13 ` [patch 3/3 v2] " Johannes Weiner
2009-05-04 13:13 ` Johannes Weiner
2009-05-04 14:31 ` Christoph Hellwig
2009-05-04 14:31 ` Christoph Hellwig
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=20090501181449.GA8912@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=hverkuil@xs4all.nl \
--cc=lethal@linux-sh.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=magnus.damm@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 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.