From: Andrew Morton <akpm@linux-foundation.org>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linux-fbdev-devel@lists.sourceforge.net, adaplas@gmail.com,
arnd@arndb.de, linux-mm@kvack.org, jayakumar.lkml@gmail.com
Subject: Re: [PATCH] video: arch specific page protection support for deferred io
Date: Wed, 24 Jun 2009 20:15:38 -0700 [thread overview]
Message-ID: <20090624201538.440806ef.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090625030933.GB13668@linux-sh.org>
On Thu, 25 Jun 2009 12:09:34 +0900 Paul Mundt <lethal@linux-sh.org> wrote:
> On Wed, Jun 24, 2009 at 07:56:47PM -0700, Andrew Morton wrote:
> > On Wed, 24 Jun 2009 19:54:13 +0900 Magnus Damm <magnus.damm@gmail.com> wrote:
> >
> > > From: Magnus Damm <damm@igel.co.jp>
> > >
> > > This patch adds arch specific page protection support to deferred io.
> > >
> > > Instead of overwriting the info->fbops->mmap pointer with the
> > > deferred io specific mmap callback, modify fb_mmap() to include
> > > a #ifdef wrapped call to fb_deferred_io_mmap(). The function
> > > fb_deferred_io_mmap() is extended to call fb_pgprotect() in the
> > > case of non-vmalloc() frame buffers.
> > >
> > > With this patch uncached deferred io can be used together with
> > > the sh_mobile_lcdcfb driver. Without this patch arch specific
> > > page protection code in fb_pgprotect() never gets invoked with
> > > deferred io.
> > >
> > > Signed-off-by: Magnus Damm <damm@igel.co.jp>
> > > ---
> > >
> > > For proper runtime operation with uncached vmas make sure
> > > "[PATCH][RFC] mm: uncached vma support with writenotify"
> > > is applied. There are no merge order dependencies.
> >
> > So this is dependent upon a patch which is in your tree, which is in
> > linux-next?
> >
> This patch is not in the sh tree, either, we wanted it to go via -mm, but
> it has the issue that it depends on pgprot_noncached() being generally
> defined, so there is a bit of an ordering mess. It could be re-posted
> with an ifdef pgprot_noncached to get it merged while we wait for the
> outstanding architectures to catch up, and this is indeed what the bulk
> of the in-tree pgprot_noncached() users in generic places end up doing
> already.
>
> Of course I can take both through the sh tree once people are happy with
> the patches.
That's OK by me - the patches are small and there's not much point in
going all formal over who-does-which-bit.
--
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-06-25 3:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 10:54 Magnus Damm
2009-06-25 2:56 ` Andrew Morton
2009-06-25 3:09 ` Paul Mundt
2009-06-25 3:15 ` Andrew Morton [this message]
2009-06-25 6:06 ` Magnus Damm
2009-06-25 7:03 ` Andrew Morton
2009-06-25 17:38 ` Paul Mundt
2009-06-25 18:12 ` Andrew Morton
2009-06-25 18:36 ` Jaya Kumar
2009-06-25 18:50 ` Paul Mundt
2009-06-26 7:50 ` Magnus Damm
2009-06-26 5:37 ` Magnus Damm
2009-06-25 18:06 ` Jaya Kumar
2009-06-25 20:57 ` Arnd Bergmann
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=20090624201538.440806ef.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adaplas@gmail.com \
--cc=arnd@arndb.de \
--cc=jayakumar.lkml@gmail.com \
--cc=lethal@linux-sh.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox