From: "Jaya Kumar" <jayakumar.lkml@gmail.com>
To: Franck Bui-Huu <vagabon.xyz@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC 2.6.19 1/1] fbdev,mm: hecuba/E-Ink fbdev driver v2
Date: Thu, 28 Dec 2006 04:53:13 +0100 [thread overview]
Message-ID: <45a44e480612271953we6fe8adg118560161579b7f9@mail.gmail.com> (raw)
In-Reply-To: <cda58cb80612220157q5433c346pccd06b8b7cbaadba@mail.gmail.com>
On 12/22/06, Franck Bui-Huu <vagabon.xyz@gmail.com> wrote:
>
> Well thinking more about it, this wouldn't work for all cache types.
> For example, if your cache is not a direct maped one, this workaround
> won't work. So this is definitely not a portable solution.
>
>From asking peterz on #mm, I think page_mkclean will do the right
thing and call something like flush_cache_page. I think that resolves
the issue which I think you identified where the end symptom on archs
with virtually tagged caches could be a line of pixels written by
userspace through one PTE remain in-cache and therefore "undisplayed"
when the kernel reads through another PTE that may fall on a different
cacheline.
Thanks,
jayakumar
--
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>
prev parent reply other threads:[~2006-12-28 3:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-11 10:46 jayakumar.lkml
2006-12-11 16:37 ` Franck Bui-Huu
2006-12-11 23:54 ` Jaya Kumar
2006-12-13 8:38 ` Franck Bui-Huu
2006-12-17 4:25 ` Jaya Kumar
2006-12-20 8:50 ` Franck Bui-Huu
2006-12-22 9:57 ` Franck Bui-Huu
2006-12-28 3:53 ` Jaya Kumar [this message]
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=45a44e480612271953we6fe8adg118560161579b7f9@mail.gmail.com \
--to=jayakumar.lkml@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vagabon.xyz@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