From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Kamble,
Nitin A" <nitin.a.kamble-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [patch] emit more information on the emulation failure
Date: Tue, 19 Jun 2007 11:11:03 +0300 [thread overview]
Message-ID: <46778F97.3090703@qumranet.com> (raw)
In-Reply-To: <1182208821.10599.4.camel-mpPvwfgnXtFHIUuj5cj4Omt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
Kamble, Nitin A wrote:
> Hi Avi,
>
> Attached is a small patch to emit little bit more information when
> emulcation reaches cannot_emulate:.
>
>
> The patch looks fine to the scripts/checkpatch.pl. It show not look to
> you in the DOS format, unless something in between us is changing the
> format of the attachment.
>
> @@ -1350,7 +1350,8 @@ twobyte_special_insn:
> goto writeback;
>
> cannot_emulate:
> - DPRINTF("Cannot emulate %02x\n", b);
> + DPRINTF("Cannot emulate %02x at 0x%lx:0x%lx\n",
> + b, ctxt->cs_base, ctxt->vcpi->rip);
> return -1;
> }
How can this compile? I think you need to replace ctxt->vcpi by ctxt->vcpu.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
prev parent reply other threads:[~2007-06-19 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 23:20 [patch] emit more information on the emulation failure Kamble, Nitin A
[not found] ` <1182208821.10599.4.camel-mpPvwfgnXtFHIUuj5cj4Omt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2007-06-19 8:11 ` Avi Kivity [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=46778F97.3090703@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.