From: Robert William Fuller <hydrologiccycle@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH]SVM CR8 undefined bug fix
Date: Thu, 17 Jan 2008 10:57:41 -0500 [thread overview]
Message-ID: <478F7AF5.80007@gmail.com> (raw)
In-Reply-To: <478F79A3.3020108@csgraf.de>
Alexander Graf wrote:
> TeLeMan wrote:
>> env->cr[8] used by SVM codes was not defined.
> As far as I remember cr8 is the very same as the TPR, so we only need to
> implement one and map the other to the value we want.
> My approach was to use the TPR and route the cr8 accesses to the tpr.
> Even though I have to admit that this might not be consistent throughout
> the code right now.
Am I to understand this is a TPR report?
next prev parent reply other threads:[~2008-01-17 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 15:34 [Qemu-devel] [PATCH]SVM CR8 undefined bug fix TeLeMan
2008-01-17 15:52 ` Alexander Graf
2008-01-17 15:57 ` Robert William Fuller [this message]
2008-01-17 16:13 ` Alexander Graf
2008-01-17 17:37 ` Bernhard Kauer
2008-02-03 2:45 ` andrzej zaborowski
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=478F7AF5.80007@gmail.com \
--to=hydrologiccycle@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).