On 11/2/06, Franck Bui-Huu <[email protected]> wrote:
Miguel Ojeda wrote:
> On 11/2/06, Franck Bui-Huu <[email protected]> wrote:
>> 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
Sorry, I don't understand what do you mean with this sentence.
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
Anyway: The data cache contains "old" data (last buffer data). Right.
The application has changed the buffer. Also OK. Why memcmp won't find
What do you mean with "data cache", "kernel fb data", ...?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Video 4 Linux]
[Linux for the blind]