From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Robert Reif <reif@earthlink.net>
Subject: Re: [Qemu-devel] sparc hflags support?
Date: Sun, 4 Nov 2007 23:47:46 +0000 [thread overview]
Message-ID: <200711042347.48438.paul@codesourcery.com> (raw)
In-Reply-To: <472E5919.80307@earthlink.net>
On Sunday 04 November 2007, Robert Reif wrote:
> 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.
If it's something that only changes rarely (e.g. when switching from early
boot to a real OS environment) you can just do a tb flush.
Does mmu/cache mode actually effect the instruction semantics?
Paul
next prev parent reply other threads:[~2007-11-04 23:47 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 [this message]
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=200711042347.48438.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=reif@earthlink.net \
/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).