On Thu, Sep 27, 2007 at 10:39:46AM +0200, Clemens Kolbitsch wrote:
> does the MEMSUFFIX macro ("kernel" / "user") mean that the memory is access
> by
> code running in ring0/ring3 or does this tell about the memory region being
> access (mem < or > TASK_SIZE / 0xc0000000)?
The former.
> and while I'm asking two other related questions I just don't quite
> understand:
>
> 1.) why does the TLB (e.g. tlb_table[CPU_MEM_INDEX][...]) have 2 different
> arrays? is this because some CPU offer different page sizes depending on a
> TASK_SIZE border or something??
It makes more sense if you realize it's kernel/user mode not address
space.
> 2.) the MMUSUFFIX macro ("mmu" / "cmmu") what does this stand for??
cmmu is used to read code to execute, IIRC (different permissions).
--
Daniel Jacobowitz
CodeSourcery
