lkml.org 
[lkml]   [2006]   [Dec]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC 2.6.19 1/1] fbdev,mm: hecuba/E-Ink fbdev driver v2
On 12/13/06, Franck Bui-Huu <vagabon.xyz@gmail.com> wrote:
> On 12/12/06, Jaya Kumar <jayakumar.lkml@gmail.com> wrote:
> > I think that PTEs set up by vmalloc are marked cacheable and via the
> > above nopage end up as cacheable. I'm not doing DMA. So the accesses
> > are through the cache so I don't think cache aliasing is an issue for
> > this case. Please let me know if I misunderstood.
> >
>
> This issue is not related to DMA: there are 2 different virtual
> addresses that can map the same physical address. If these 2 virtual
> addresses use 2 different data cache entries then you have a cache
> aliasing issue. In your case the 2 different virtual addresses are (1)

Ok. I now see what you mean. In typical cases, only one path is used
to write. Meaning an app will decide to use the mmap path or the slow
write path and the kernel only ever reads from its pte entry (unless
fbcon is used which is not suited for this type of display). But you
are right that it is possible for a situation to arise where one app
does mmap and another is doing write. My hope is that something takes
care of flushing the data cache for me in this case. Do you recommend
I add something to force that? I'm worried about having an fbdev
driver that is too involved with mm.

Thanks,
jayakumar


> the one got by the kernel (returned by vmalloc) (2) the one got by the
> application (returned by mmap).
>
> Hope that helps.
> --
> Franck
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-12-17 05:29    [from the cache]
©2003-2014 Jasper Spaans. Advertise on this site