From: "Woods, Brian" <Brian.Woods@amd.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Wei Liu" <wei.liu2@citrix.com>,
"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>,
Xen-devel <xen-devel@lists.xen.org>,
"Paul Durrant" <paul.durrant@citrix.com>,
"Jan Beulich" <JBeulich@suse.com>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Woods, Brian" <Brian.Woods@amd.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH 1/2] x86/svm: Improve diagnostics when __get_instruction_length_from_list() fails
Date: Fri, 30 Nov 2018 17:13:37 +0000 [thread overview]
Message-ID: <20181130171333.GB5122@amd.com> (raw)
In-Reply-To: <1543597640-28870-2-git-send-email-andrew.cooper3@citrix.com>
On Fri, Nov 30, 2018 at 05:07:19PM +0000, Andy Cooper wrote:
> Sadly, a lone:
>
> (XEN) emulate.c:156:d2v0 __get_instruction_length_from_list: Mismatch between expected and actual instruction: eip = fffff804564139c0
>
> on the console is of no use trying to identify what went wrong. Dump as much
> state as we can to help identify what went wrong.
>
> Reported-by: Paul Durrant <paul.durrant@citrix.com>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Brian Woods <brian.woods@amd.com>
--
Brian Woods
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-11-30 17:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 17:07 [PATCH 0/2] Fixes to RDTSCP interception Andrew Cooper
2018-11-30 17:07 ` [PATCH 1/2] x86/svm: Improve diagnostics when __get_instruction_length_from_list() fails Andrew Cooper
2018-11-30 17:13 ` Woods, Brian [this message]
2018-12-03 9:10 ` Paul Durrant
2018-12-03 10:41 ` Jan Beulich
2018-12-03 10:32 ` Jan Beulich
2018-12-03 11:45 ` Andrew Cooper
2018-11-30 17:07 ` [PATCH 2/2] x86/hvm: Corrections to RDTSCP intercept handling Andrew Cooper
2018-11-30 17:19 ` Woods, Brian
2018-12-03 9:17 ` Paul Durrant
2018-12-03 11:13 ` Andrew Cooper
2018-12-03 11:23 ` Paul Durrant
2018-12-03 10:47 ` Jan Beulich
2018-12-13 6:24 ` Tian, Kevin
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=20181130171333.GB5122@amd.com \
--to=brian.woods@amd.com \
--cc=JBeulich@suse.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=paul.durrant@citrix.com \
--cc=roger.pau@citrix.com \
--cc=wei.liu2@citrix.com \
--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 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.