From: fche@redhat.com (Frank Ch. Eigler)
To: "james chen" <james_ch1@sina.com>
Cc: <ecos-discuss@sources.redhat.com>, sid@sources.redhat.com
Subject: Re: [ECOS] Arm emulator
Date: Fri, 07 Sep 2001 11:43:00 -0000 [thread overview]
Message-ID: <o5y9nqyh83.fsf@toenail.toronto.redhat.com> (raw)
In-Reply-To: <000701c12bb2$898125c0$c408aa0a@inc.inventec>
"james chen" <james_ch1@sina.com> writes on ecos-discuss:
: [...] I find that it was ARM instructions emulating that takes many
: PC CPU resource. In my PC( CE333) I only get 1 MIPS in emulating ARM
: instructions [using an enhanced gdb/arm simulator], are there any
: way to improve it. [...]
A target:host instruction ratio of 1:100 is about typical for an
instruction set simulator that uses ordinary fetch/decode/execute
algorithms. Advanced interpretation techniques like cached decode
structures, native host translation, can help a lot, but are pretty
hard to create.
The sid simulator uses an ARM kernel generated by the cgen tool (both
on http://sources.redhat.com/ ), and it does have a small degree of
this sort of thing, but I don't know how it performs in comparison to
the old armulator snapshot (gdb's arm sim). sid has a feature that
may assist simulation speed in an indirect way: state save/restore,
which lets you theoretically rerun a program from a saved snapshot.
That saves time in skipping e.g. initialization.
Apart from these, and simple mechanical improvements (like compiling
everything with maximum optimization), I can't think of a way of
significantly improving speed.
- FChE
parent reply other threads:[~2001-09-07 11:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <000701c12bb2$898125c0$c408aa0a@inc.inventec>]
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=o5y9nqyh83.fsf@toenail.toronto.redhat.com \
--to=fche@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=james_ch1@sina.com \
--cc=sid@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).