On Thursday 27 September 2007 17:27:32 Daniel Jacobowitz wrote:
> On Thu, Sep 27, 2007 at 05:02:46PM +0200, Clemens Kolbitsch wrote:
> > but will kernel mode always use the TLB[0] for address translation (even
> > for addresses at e.g. 0x0800) and user mode TLB[1] (even for e.g.
> > 0xc000abcd)
On Thu, Sep 27, 2007 at 05:02:46PM +0200, Clemens Kolbitsch wrote:
> but will kernel mode always use the TLB[0] for address translation (even for
> addresses at e.g. 0x0800) and user mode TLB[1] (even for e.g.
> 0xc000abcd)? (or the other way round...)
Which set of TLBs are used depends comp
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 / 0xc000)?
>
> The former.
ok :-)
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 / 0xc000)?
The former.
> and wh
hi guys!
just a short question:
in softmmu_header.h, for example in function
glue(glue(ld, USUFFIX), MEMSUFFIX)(target_ulong ptr)
which boils down to be included in (e.g.)
op_ldl_kernel_T0_A0
or
op_ldub_user_T0_A0
or
...
does the MEMSUFFIX macro ("kernel" / "user") mean that the memory is acc
