From: Daniel Jacobowitz <drow@false.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] softmmu macro meaning
Date: Thu, 27 Sep 2007 08:50:11 -0400 [thread overview]
Message-ID: <20070927125011.GA29613@caradoc.them.org> (raw)
In-Reply-To: <200709271039.46589.clemens.kol@gmx.at>
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
next prev parent reply other threads:[~2007-09-27 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 8:39 [Qemu-devel] softmmu macro meaning Clemens Kolbitsch
2007-09-27 12:50 ` Daniel Jacobowitz [this message]
[not found] <20070927140247.10904gmx1@mx066.gmx.net>
2007-09-27 15:02 ` Clemens Kolbitsch
2007-09-27 15:27 ` Daniel Jacobowitz
2007-09-27 16:47 ` Clemens Kolbitsch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070927125011.GA29613@caradoc.them.org \
--to=drow@false.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.