From: "Lai, Paul C" <paul.c.lai@intel.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Altp2m misbehavior
Date: Mon, 2 May 2016 16:28:42 +0000 [thread overview]
Message-ID: <8CA46881B83C354B99AD61C20C93EB1BD509B7@ORSMSX109.amr.corp.intel.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 533 bytes --]
Hello list:
Been playing with the altp2m code and noticed that it's not behaving in Xen 4.7 tree.
Two changesets have been identified as where the be behavior changes.
The change is commit bd2239d9fa975a1ee5bcd27c218ae042cd0a57bc,
x86/HVM: always intercept #AC and #DB
where an executable goes from working to crashing after a 10+ hypercalls.
The second change is in commit 484c14b7254e8d8936c05e3c28e332ea825c0155:
x86/vmx: enable PML by default
This hangs the VM guest on the first few hypercalls.
-Paul
[-- Attachment #1.2: Type: text/html, Size: 2686 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2016-05-02 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 16:28 Lai, Paul C [this message]
2016-05-03 7:35 ` Altp2m misbehavior Jan Beulich
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=8CA46881B83C354B99AD61C20C93EB1BD509B7@ORSMSX109.amr.corp.intel.com \
--to=paul.c.lai@intel.com \
--cc=xen-devel@lists.xenproject.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).