From: wogiz@openmailbox.org
To: Jan Beulich <jbeulich@suse.com>
Cc: andrew.cooper3@citrix.com, mihai.dontu@gmail.com,
xen-devel@lists.xen.org
Subject: Re: Bug in x86 instruction emulator?
Date: Fri, 08 Apr 2016 03:43:32 +0200 [thread overview]
Message-ID: <9b8767126bb2eaafb2d46c05a3491f9a@openmailbox.org> (raw)
In-Reply-To: <5705CE4902000078000E5F2E@prv-mh.provo.novell.com>
On 2016-04-07 04:04, Jan Beulich wrote:
> We'd need to know which exact exception (including error code and,
> in the case of #PF, CR2 value) gets raised to the guest by what
> specific piece of code in the hypervisor. That'll likely mean some
> instrumentation of the hypervisor code.
>
> Jan
No problem with instrumentation as it's not a production system.
I don't have the knowledge to write code, but if a patch can be created
or if only a few lines of code is required, I can edit source files
manually, rebuild, install Xen and collect the required information.
William Z.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-08 1:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 23:38 Bug in x86 instruction emulator? wogiz
2016-04-05 23:57 ` Mihai Donțu
2016-04-06 0:02 ` Mihai Donțu
2016-04-06 1:48 ` wogiz
2016-04-06 1:26 ` wogiz
2016-04-06 8:55 ` Andrew Cooper
2016-04-07 1:26 ` wogiz
2016-04-07 2:04 ` Jan Beulich
2016-04-08 1:43 ` wogiz [this message]
2016-04-15 17:33 ` wogiz
2016-04-15 17:44 ` Andrew Cooper
2016-04-16 4:06 ` wogiz
2016-05-04 16:02 ` Jan Beulich
2016-05-04 16:04 ` Wei Liu
2016-05-04 16:06 ` Andrew Cooper
2016-05-17 16:53 ` William Z.
2016-05-17 17:03 ` Andrew Cooper
2016-05-18 9:12 ` Jan Beulich
2016-05-20 16:44 ` William Z.
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=9b8767126bb2eaafb2d46c05a3491f9a@openmailbox.org \
--to=wogiz@openmailbox.org \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=mihai.dontu@gmail.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 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).