From: Avi Kivity <avi@redhat.com>
To: Mohammed Gamal <m.gamal005@gmail.com>
Cc: kvm@vger.kernel.org, mtosatti@redhat.com
Subject: Re: [PATCH] x86 emulator: Add IRET instruction
Date: Wed, 28 Jul 2010 07:20:45 +0300 [thread overview]
Message-ID: <4C4FB01D.50503@redhat.com> (raw)
In-Reply-To: <1280272001-1415-1-git-send-email-m.gamal005@gmail.com>
On 07/28/2010 02:06 AM, Mohammed Gamal wrote:
> Ths patch adds IRET instruction (opcode 0xcf).
> Currently, only IRET in real mode is emulated. Protected mode support is to be added later if needed.
>
> @@ -1778,6 +1778,69 @@ static int emulate_popa(struct x86_emulate_ctxt *ctxt,
> return rc;
> }
>
> +static int emulate_iret_real(struct x86_emulate_ctxt *ctxt,
> + struct x86_emulate_ops *ops)
> +{
> + struct decode_cache *c =&ctxt->decode;
> + int rc = X86EMUL_CONTINUE;
> + unsigned long temp_eip = 0;
> + unsigned long temp_eflags = 0;
> + unsigned long mask = EFLG_CF | EFLG_PF | EFLG_AF | EFLG_ZF | EFLG_SF | EFLG_TF |
> + EFLG_IF | EFLG_DF | EFLG_OF | EFLG_IOPL | EFLG_NT | EFLG_RF |
> + EFLG_AC | EFLG_ID | (1<< 1); /* Last one is the reserved bit */
> + unsigned long vm86_mask = EFLG_VM | EFLG_VIF | EFLG_VIP;
> +
> + /* TODO: Add stack limit check */
> +
> + rc = emulate_pop(ctxt, ops,&temp_eip, c->op_bytes);
> +
> + if (rc != X86EMUL_CONTINUE)
> + return rc;
> +
> + if (temp_eip& ~0xffff) {
> + emulate_gp(ctxt, 0);
> + return X86EMUL_PROPAGATE_FAULT;
> + }
> +
> + c->eip = temp_eip;
> +
> + rc = emulate_pop_sreg(ctxt, ops, VCPU_SREG_CS);
> +
> + if (rc != X86EMUL_CONTINUE)
> + return rc;
> +
> + rc = emulate_pop(ctxt, ops,&temp_eflags, c->op_bytes);
If this pop fails, the emulate_pop_sreg() will already have been
committed and the cs will be corrupted. That's a preexisting problem,
however, we can fix it later.
> +
> + if (rc != X86EMUL_CONTINUE)
> + return rc;
> +
> + if (c->op_bytes == 4) {
> + temp_eflags = ((temp_eflags& mask) | (ctxt->eflags& vm86_mask));
> + ctxt->eflags = temp_eflags;
Can combine to a single assignment instead of two.
> + } else if (c->op_bytes == 2) {
> + temp_eflags&= ~0xfffd; /* Do not clear reserved bit 1 */
> + ctxt->eflags |= temp_eflags;
If temp_eflags has CF clear, but ctxt->eflags has CF set, we end up with
CF set, incorrectly. Need to drop the low 16 bits from ctxt->eflags.
> + }
> +
Need also to ensure reserved bits are set to their required values,
something like
ctxt->eflags &= ~EFLG_RESERVED_0_MASK; (0xffc0802a)
ctxt->eflags |= EFLG_RESERVERD_1_MASK; (0x2)
> + return rc;
> +}
> +
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-07-28 4:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 23:06 [PATCH] x86 emulator: Add IRET instruction Mohammed Gamal
2010-07-28 4:20 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-07-28 9:38 Mohammed Gamal
2010-07-28 10:30 ` Avi Kivity
2010-07-28 13:30 ` Paolo Bonzini
2010-07-28 13:49 ` Paolo Bonzini
2010-07-28 17:15 ` Marcelo Tosatti
2010-07-25 19:20 Mohammed Gamal
2010-07-25 23:59 ` Paolo Bonzini
2010-07-26 0:07 ` Mohammed Gamal
2010-07-26 3:09 ` Wei Yongjun
2010-07-26 8:47 ` Paolo Bonzini
2010-07-26 9:00 ` Avi Kivity
2010-07-26 9:31 ` Paolo Bonzini
2010-07-26 9:32 ` Paolo Bonzini
2010-07-26 11:38 ` Avi Kivity
2010-07-25 19:18 Mohammed Gamal
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=4C4FB01D.50503@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=m.gamal005@gmail.com \
--cc=mtosatti@redhat.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