From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: nitin.a.kamble-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [patch] (big) real mode emulation - mul instruction from group 3
Date: Wed, 31 Oct 2007 02:53:01 +0200 [thread overview]
Message-ID: <4727D1ED.7070609@qumranet.com> (raw)
In-Reply-To: <1193791027.9258.8.camel-mpPvwfgnXtFHIUuj5cj4Omt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
Nitin A Kamble wrote:
> Hi Avi,
> Attached is the patch to implement mul instruction from the group 3
> opcodes.
>
> diff --git a/drivers/kvm/x86_emulate.c b/drivers/kvm/x86_emulate.c
> index 3959c20..5815128 100644
> --- a/drivers/kvm/x86_emulate.c
> +++ b/drivers/kvm/x86_emulate.c
> @@ -1034,6 +1034,8 @@ static inline int emulate_grp3(struct
> x86_emulate_ctxt *ctxt,
> case 3: /* neg */
> emulate_1op("neg", c->dst, ctxt->eflags);
> break;
> + case 4: /* mul */
> + emulate_1op("mul", c->dst, ctxt->eflags);
> default:
> DPRINTF("Cannot emulate %02x\n", c->b);
> rc = X86EMUL_UNHANDLEABLE;
This is missing a "break;".
How are you testing these patches?
--
Any sufficiently difficult bug is indistinguishable from a feature.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-31 0:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 0:37 [patch] (big) real mode emulation - mul instruction from group 3 Nitin A Kamble
[not found] ` <1193791027.9258.8.camel-mpPvwfgnXtFHIUuj5cj4Omt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2007-10-31 0:53 ` Avi Kivity [this message]
[not found] ` <4727D1ED.7070609-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-31 2:37 ` Nitin A Kamble
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=4727D1ED.7070609@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=nitin.a.kamble-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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