qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] softmmu macro meaning


From: Daniel Jacobowitz
Subject: Re: [Qemu-devel] softmmu macro meaning
Date: Thu, 27 Sep 2007 08:50:11 -0400
User-agent: Mutt/1.5.15 (2007-04-09)

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]