From: Paul Mundt <lethal@linux-sh.org>
To: Jaya Kumar <jayakumar.lkml@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
magnus.damm@gmail.com, linux-fbdev-devel@lists.sourceforge.net,
adaplas@gmail.com, arnd@arndb.de, linux-mm@kvack.org
Subject: Re: [PATCH] video: arch specific page protection support for deferred io
Date: Fri, 26 Jun 2009 03:50:47 +0900 [thread overview]
Message-ID: <20090625185047.GA25916@linux-sh.org> (raw)
In-Reply-To: <45a44e480906251136l3a83188bm3f730534f89d00cb@mail.gmail.com>
On Fri, Jun 26, 2009 at 02:36:23AM +0800, Jaya Kumar wrote:
> On Fri, Jun 26, 2009 at 2:12 AM, Andrew Morton<akpm@linux-foundation.org> wrote:
> > On Fri, 26 Jun 2009 02:38:06 +0900
> > Paul Mundt <lethal@linux-sh.org> wrote:
> >
> >> On Thu, Jun 25, 2009 at 12:03:59AM -0700, Andrew Morton wrote:
> >> > On Thu, 25 Jun 2009 15:06:24 +0900 Magnus Damm <magnus.damm@gmail.com> wrote:
> >> > > There are 3 levels of dependencies:
> >> > > 1: pgprot_noncached() patches from Arnd
> >> > > 2: mm: uncached vma support with writenotify
> >> > > 3: video: arch specfic page protection support for deferred io
> >> > >
> >> > > 2 depends on 1 to compile, but 3 (this one) is disconnected from 2 and
> >> > > 1. So this patch can be merged independently.
> > <hunts around and finds #2>
> >
> > I don't really understand that one. ?Have we heard fro Jaya recently?
> >
>
> He's been having some personal problems so he's been quiet. :-)
>
> Magnus's defio changes, #3 look fine to me. I don't know much about #2
> but what I understood was that the previous mmap_region code was
> unintentionally turning caching back on when it did the writenotify
> test and I guess Magnus's goal with the patch is to make sure that
> address range is left uncached since sh_mobile uses DMA to transfer
> the framebuffer and he might have encountered coherency issues there?
>
Correct. This could have been documented a bit better, but yes, the issue
is that when the writenotify test kicks in the vma silently loses its
uncachedness which leads to the aforementioned runtime behaviour issues.
--
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 18:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 10:54 [PATCH] video: arch specific page protection support for deferred io Magnus Damm
2009-06-25 2:56 ` Andrew Morton
2009-06-25 3:09 ` Paul Mundt
2009-06-25 3:15 ` Andrew Morton
2009-06-25 6:06 ` Magnus Damm
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:36 ` Jaya Kumar
2009-06-25 18:50 ` Paul Mundt [this message]
2009-06-26 7:50 ` Magnus Damm
2009-06-26 7:50 ` Magnus Damm
2009-06-26 5:37 ` Magnus Damm
2009-06-26 5:37 ` Magnus Damm
2009-06-25 18:06 ` Jaya Kumar
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=20090625185047.GA25916@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=adaplas@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=jayakumar.lkml@gmail.com \
--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 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.