mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: Miguel Ojeda <maxextreme@gmail.com>
Cc: Franck <vagabon.xyz@gmail.com>,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH update6] drivers: add LCD support
Date: Thu, 02 Nov 2006 15:26:14 +0100	[thread overview]
Message-ID: <454A0006.4090505@innova-card.com> (raw)
In-Reply-To: <653402b90611020544l6e5ded94hc4c932fc1442fcb0@mail.gmail.com>

Miguel Ojeda wrote:
> On 11/2/06, Franck Bui-Huu <vagabon.xyz@gmail.com> wrote:
>> Hi
>>
>> Miguel Ojeda Sandonis wrote:
>> > Andrew, here it is the coding style fixes. Thanks you.
>> >
>> > I think the driver is getting ready for freeze until
>> > 2.6.20-rc1 (if anyone sees something wrong), so I will
>> > try to send just minor fixes like this.
>>
>> :)
>>
>> Again, any thoughts on cache aliasing ?
>>
> 
> If you have seen something wrong, please tell. What are you thinking about?

Sorry for the short/fast question. I'm wondering how does the cache
behave here. You have 2 virtual addresses that point to the same
location in physical RAM: kernel frame buffer which has a kernel
virtual address and the vma you're returning when an application mmap
the device. This last address is a user virtual address and is
different from the first one.

Now let's say that some of the kernel frame buffer data are in the
data cache and never be invalidate during this example. The
application updates its mmapped frame buffer. During the refresh time,
the kernel take a look to its frame buffer to check if something
change. Since the 'old' data are still in the data cache and are
valid, the kernel will use them instead of the new one set by the
application.

		Franck

  reply	other threads:[~2006-11-02 14:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-01  1:40 Miguel Ojeda Sandonis
2006-11-02  8:51 ` Franck Bui-Huu
2006-11-02 13:44   ` Miguel Ojeda
2006-11-02 14:26     ` Franck Bui-Huu [this message]
2006-11-02 14:44       ` Miguel Ojeda
2006-11-02 19:13         ` Andrew Morton
2006-11-02 19:33           ` Miguel Ojeda
2006-11-02 20:04             ` Andrew Morton
2006-11-03  0:00               ` David Miller
2006-11-03  6:45                 ` Miguel Ojeda

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=454A0006.4090505@innova-card.com \
    --to=vagabon.xyz@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxextreme@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

all inboxes | Powered by JetHome®