mmap hw behavior

[Michal Simek <michal.simek@petalogix.com>]

Hi All,

I wrote one email about my problem with mmap on Microblaze. (Especially
mmap01 ltp test)
I need to know how mmap should work with MMU or what the correct steps are.

When I open temp file in application is the kernel create file descriptor table and kernel take
care about setup tlb which are needed. Application get back just file descriptor.

When I call calloc it is called brk kernel syscall and is created one tlb for this place. 
Brk allocate more memory than is requested by calloc. Application got pointer to that memory place.


When I call mmap for that open file with pointer to calloc place (first parameter, + length zero)
it should be one tlb invalidation for calloc and new tlb which connect open file. 
We check it and we don't have any tlb invalidation that's why I think that kernel do different thigs.
Or is it there any copying? Or anything different?

Thanks for clarification,
Michal

-- 
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663