On Thursday 27 September 2007 16:01:08 [EMAIL PROTECTED] 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.
ok :-)
>
> > 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.
ok... so it's really 1 for user-mode and 1 for kernel-mode...
but will kernel mode always use the TLB[0] for address translation (even for
addresses at e.g. 0x0800ffff) and user mode TLB[1] (even for e.g.
0xc000abcd)? (or the other way round...)
>
> > 2.) the MMUSUFFIX macro ("mmu" / "cmmu") what does this stand for??
>
> cmmu is used to read code to execute, IIRC (different permissions).
ok, thanks!!
