From: Thiemo Seufer <ths@networkno.de>
To: "J. Mayer" <l_indien@magic.fr>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] support more than 2 execution modes
Date: Mon, 26 Mar 2007 09:49:40 +0100 [thread overview]
Message-ID: <20070326084940.GA23564@networkno.de> (raw)
In-Reply-To: <1174892411.6794.18.camel@rapid>
J. Mayer wrote:
> It appears that some targets may need more than the 2 "standard"
> execution modes.
> For example, PowerPC 64 has 3 execution modes: hypervisor, supervisor
> and problem state.
> Another example is alpha which has 4 execution modes (even if Linux
> seems to use only two of them).
>
> My proposal is to increase the number of the tlb_tables entries in a way
> that would be selected at compile time in order to keep good
> performances for other emulated targets that do not need this feature.
>
> You'll find attached a short patch implementing it. With this patch, one
> would just have to properly define CPU_MEM_INDEX and is_user flags for
> those targets.
>
> Please comment.
Looks good to me, as it will help to implement MIPS supervisor mode
some day. :-)
Thiemo
prev parent reply other threads:[~2007-03-26 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 7:00 [Qemu-devel] [RFC] support more than 2 execution modes J. Mayer
2007-03-26 8:49 ` Thiemo Seufer [this message]
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=20070326084940.GA23564@networkno.de \
--to=ths@networkno.de \
--cc=l_indien@magic.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).