From: Eduardo Habkost <ehabkost@redhat.com>
To: Todd Eisenberger <teisenbe@google.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH] x86: Correct translation of some rdgsbase and wrgsbase encodings
Date: Fri, 29 Sep 2017 16:43:29 -0300 [thread overview]
Message-ID: <20170929194329.GO21016@localhost.localdomain> (raw)
In-Reply-To: <CAP26EVRNVb=Mq=O3s51w7fDhGVmf-e3XFFA73MRzc5b4qKBA4g@mail.gmail.com>
On Thu, Sep 28, 2017 at 10:17:06AM -0700, Todd Eisenberger via Qemu-devel wrote:
> It looks like there was a transcription error when writing this code
> initially. The code previously only decoded src or dst of rax. This
> resolves
> https://bugs.launchpad.net/qemu/+bug/1719984.
>
> Signed-off-by: Todd Eisenberger <teisenbe@google.com>
> ---
> target/i386/translate.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/target/i386/translate.c b/target/i386/translate.c
> index a8986f4c1a..7b920115f9 100644
> --- a/target/i386/translate.c
> +++ b/target/i386/translate.c
> @@ -8155,9 +8155,9 @@ static target_ulong disas_insn(DisasContext *s,
> CPUState *cpu)
The patch is corrupted due to line wrapping. I recommend using
git-send-email to avoid that.
I'm queueing it on x86-next after fixing it manually.
> break;
>
> case 0xc0 ... 0xc7: /* rdfsbase (f3 0f ae /0) */
> - case 0xc8 ... 0xc8: /* rdgsbase (f3 0f ae /1) */
> + case 0xc8 ... 0xcf: /* rdgsbase (f3 0f ae /1) */
> case 0xd0 ... 0xd7: /* wrfsbase (f3 0f ae /2) */
> - case 0xd8 ... 0xd8: /* wrgsbase (f3 0f ae /3) */
> + case 0xd8 ... 0xdf: /* wrgsbase (f3 0f ae /3) */
> if (CODE64(s)
> && (prefixes & PREFIX_REPZ)
> && !(prefixes & PREFIX_LOCK)
>
--
Eduardo
next prev parent reply other threads:[~2017-09-29 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 17:17 [Qemu-devel] [PATCH] x86: Correct translation of some rdgsbase and wrgsbase encodings Todd Eisenberger
2017-09-28 17:20 ` Richard Henderson
2017-09-29 19:43 ` Eduardo Habkost [this message]
2017-09-29 20:28 ` Todd Eisenberger
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=20170929194329.GO21016@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=teisenbe@google.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 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).