[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] softmmu macro meaning
From: |
Clemens Kolbitsch |
Subject: |
[Qemu-devel] softmmu macro meaning |
Date: |
Thu, 27 Sep 2007 10:39:46 +0200 |
User-agent: |
KMail/1.9.6 |
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 access by
code running in ring0/ring3 or does this tell about the memory region being
access (mem < or > TASK_SIZE / 0xc0000000)?
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??
2.) the MMUSUFFIX macro ("mmu" / "cmmu") what does this stand for??
Thanks!!!
Clemens
- [Qemu-devel] softmmu macro meaning,
Clemens Kolbitsch <=