From: Robert Reif <reif@earthlink.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] sparc hflags support?
Date: Sun, 04 Nov 2007 18:43:21 -0500 [thread overview]
Message-ID: <472E5919.80307@earthlink.net> (raw)
I'm looking at adding more complete support for different sparc32
CPUs, MMUs, cache controllers and systems.
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.
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.
next reply other threads:[~2007-11-04 23:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 23:43 Robert Reif [this message]
2007-11-04 23:47 ` [Qemu-devel] sparc hflags support? Paul Brook
2007-11-05 16:02 ` Blue Swirl
2007-11-05 15:55 ` Blue Swirl
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=472E5919.80307@earthlink.net \
--to=reif@earthlink.net \
--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).