From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Tim Deegan <tim@xen.org>
Cc: Kevin Tian <kevin.tian@intel.com>, Keir Fraser <keir@xen.org>,
Jan Beulich <JBeulich@suse.com>,
Eddie Dong <eddie.dong@intel.com>,
Xen-devel <xen-devel@lists.xen.org>,
Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: [PATCH for-4.5 2/2] x86/hvm: Improve "Emulation failed @" error messages
Date: Fri, 26 Sep 2014 13:09:24 +0100 [thread overview]
Message-ID: <54255774.20109@citrix.com> (raw)
In-Reply-To: <20140926120545.GB35563@deinos.phlegethon.org>
On 26/09/14 13:05, Tim Deegan wrote:
> At 11:10 +0100 on 26 Sep (1411726207), Andrew Cooper wrote:
>> +static const char *guest_x86_mode_to_str(int mode)
>> +{
>> + switch ( mode )
>> + {
>> + case 0:
>> + return "Real";
>> + case 1:
>> + return "v8086";
>> + case 2:
> return "16bit"?
>
> Otherwise, Reviewed-by: Tim Deegan <tim@xen.org>
>
> While you're respinning, could you also shorten all of these strings
> (e.g. to real/vm86/16b/32b/64b), and trim the rest of the line,
> something like:
>
> (d1) MMIO emulation failed: d1v0 64b @ 0008:ffff82d080102fea: 48 63 8d 40 ff ff ff
>
> You can keep the reviewed-by regardless of whatever cosmetic changes.
>
> Cheers,
>
> Tim.
As identified in the other thread, "16bit" is misleading as the
instruction bytes are actually 32bit code in a 16bit segment.
I am not sure what the best solution here is. Perhaps we can trust
anyone capable of interpreting this error to know that "16b" != "Real"
or "v86" when it comes to decoding the instruction.
~Andrew
next prev parent reply other threads:[~2014-09-26 12:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 10:10 [PATCH for-4.5 0/2] Improve "Emulation failed" error message Andrew Cooper
2014-09-26 10:10 ` [PATCH for-4.5 1/2] xen/vsprintf: Introduce %*ph extended format specifier for hex buffers Andrew Cooper
2014-09-26 11:32 ` Jan Beulich
2014-09-26 12:16 ` Andrew Cooper
2014-09-26 12:31 ` Jan Beulich
2014-09-26 12:32 ` Andrew Cooper
2014-09-26 11:49 ` Tim Deegan
2014-09-26 11:57 ` Jan Beulich
2014-09-26 10:10 ` [PATCH for-4.5 2/2] x86/hvm: Improve "Emulation failed @" error messages Andrew Cooper
2014-09-26 11:39 ` Jan Beulich
2014-09-26 12:04 ` Andrew Cooper
2014-09-26 12:36 ` Jan Beulich
2014-09-26 12:53 ` Andrew Cooper
2014-09-26 12:05 ` Tim Deegan
2014-09-26 12:09 ` Andrew Cooper [this message]
2014-09-26 12:41 ` Tim Deegan
2014-09-26 12:57 ` Andrew Cooper
2014-09-26 13:06 ` Jan Beulich
2014-09-26 13:16 ` Andrew Cooper
2014-09-26 13:32 ` Jan Beulich
2014-09-26 14:15 ` [PATCH for-4.5 0/2] Improve "Emulation failed" error message Konrad Rzeszutek Wilk
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=54255774.20109@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=eddie.dong@intel.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).