From: Paolo Bonzini <pbonzini@redhat.com>
To: Roman Kapl <rka@sysgo.com>
Cc: Rudolf Marek <rudolf.marek@sysgo.com>,
Richard Henderson <rth@twiddle.net>,
Eduardo Habkost <ehabkost@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Clear RF on SYSCALL instruction
Date: Fri, 19 Oct 2018 14:27:07 +0200 [thread overview]
Message-ID: <e408c3b6-bba1-d121-a2b0-ab0507285091@redhat.com> (raw)
In-Reply-To: <20181019122449.26387-1-rka@sysgo.com>
On 19/10/2018 14:24, Roman Kapl wrote:
> From: Rudolf Marek <rudolf.marek@sysgo.com>
>
> Fix the SYSCALL instruction in 64-bit (long mode). The RF flag
> should be cleared in R11 as well as in the RFLAGS. Intel
> and AMD CPUs behave same. AMD has this documented in the
> APM vol 3.
>
> Signed-off-by: Roman Kapl <rka@sysgo.com>
> Signed-off-by: Rudolf Marek <rudolf.marek@sysgo.com>
> ---
> target/i386/seg_helper.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/target/i386/seg_helper.c b/target/i386/seg_helper.c
> index 33714bc6e1..63e265cb38 100644
> --- a/target/i386/seg_helper.c
> +++ b/target/i386/seg_helper.c
> @@ -991,11 +991,11 @@ void helper_syscall(CPUX86State *env, int next_eip_addend)
> int code64;
>
> env->regs[R_ECX] = env->eip + next_eip_addend;
> - env->regs[11] = cpu_compute_eflags(env);
> + env->regs[11] = cpu_compute_eflags(env) & ~RF_MASK;
>
> code64 = env->hflags & HF_CS64_MASK;
>
> - env->eflags &= ~env->fmask;
> + env->eflags &= ~(env->fmask | RF_MASK);
> cpu_load_eflags(env, env->eflags, 0);
> cpu_x86_load_seg_cache(env, R_CS, selector & 0xfffc,
> 0, 0xffffffff,
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2018-10-19 12:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 12:24 [Qemu-devel] [PATCH] Clear RF on SYSCALL instruction Roman Kapl
2018-10-19 12:27 ` Paolo Bonzini [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=e408c3b6-bba1-d121-a2b0-ab0507285091@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rka@sysgo.com \
--cc=rth@twiddle.net \
--cc=rudolf.marek@sysgo.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).