From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] sparc hflags support?
Date: Mon, 5 Nov 2007 17:55:47 +0200 [thread overview]
Message-ID: <f43fc5580711050755w5a0bb1bdk60b7c8c543242457@mail.gmail.com> (raw)
In-Reply-To: <472E5919.80307@earthlink.net>
On 11/5/07, Robert Reif <reif@earthlink.net> wrote:
> I'm looking at adding more complete support for different sparc32
> CPUs, MMUs, cache controllers and systems.
Great! The only problems I see are that OpenBIOS support needs to be
added for the new CPUs and supporting all CPUs with one image may
become a bit complex.
> Each CPU/MMU/cache controller combination is slightly different and
> requires its own unique state. For example the two CPUs currently
> supported save the boot mode in different bits in the MMU control
> register: 0x2000 for the SuperSparc and 0x4000 for the TurboSparc.
> Others bits will need to be saved in the MMU and cache controllers
> as better hardware emulation is added.
I think other targets have better design for supporting different CPU
types, for example MIPS and PPC.
> It looks like other architectures handle this by computing hflags
> in the target directories but sparc determines the flags value to save
> in common code.
>
> Are there plans to add hflags support to sparc? I'm willing work
> on it but I don't have the experience yet to tackle a job like this
> without help.
It could bring some performance benefit. Just try to move the tb flags
computation to op_helper.c. Every time hflags elements change,
recompute the flags. I'd be happy to try to help you.
prev parent reply other threads:[~2007-11-05 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 23:43 [Qemu-devel] sparc hflags support? Robert Reif
2007-11-04 23:47 ` Paul Brook
2007-11-05 16:02 ` Blue Swirl
2007-11-05 15:55 ` Blue Swirl [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=f43fc5580711050755w5a0bb1bdk60b7c8c543242457@mail.gmail.com \
--to=blauwirbel@gmail.com \
--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).