From: Tom Musta <tommusta@gmail.com>
To: Thomas Huth <thuth@linux.vnet.ibm.com>, Alexander Graf <agraf@suse.de>
Cc: "qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] target-ppc: Problem with mtmsr emulation
Date: Fri, 28 Mar 2014 12:56:26 -0500 [thread overview]
Message-ID: <5335B7CA.8010909@gmail.com> (raw)
In-Reply-To: <533588FC.70807@gmail.com>
On 3/28/2014 9:36 AM, Tom Musta wrote:
> I agree with Alex that a flags based approach could be used to support the L bit for
> Book III-S models and to ignore the L bit for Book III-E models. The question is
> which flag(s) can we use? Let me see if I can find out.
I looked at this a bit more. I do not see any good correlation with the existing
instruction flags.
I do see some good correlation with the exception flags. But there are problems: One
challenge that I see is that the exception flags are not (currently) available in the
context structure passed to the generators (DisasContext). The other problem is that
this has the same brittleness that Alex was observing about adding new models and
needing to remember all the little bits to be set (different thread yesterday).
Given this, I think a reasonable way to proceed would be to:
(a) add an explicit instruction flag for L bit support (e.g. PPC2_MTMSR_L)
(b) remove the bit from the reserved bits mask
(c) add some additional logic to the mtmsr[d] generators to gate the L=1 path.
(d) add the new flag to the more recent models that support Book III-S.
And I still think there might be a bug in the L=0 Book III-S path.
prev parent reply other threads:[~2014-03-28 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 8:16 [Qemu-devel] target-ppc: Problem with mtmsr emulation Thomas Huth
2014-03-28 10:25 ` Alexander Graf
2014-03-28 12:02 ` Thomas Huth
2014-03-28 14:36 ` [Qemu-devel] [Qemu-ppc] " Tom Musta
2014-03-28 17:56 ` Tom Musta [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=5335B7CA.8010909@gmail.com \
--to=tommusta@gmail.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.