From: Abhiroop Dabral <abhiroop.dabral@gmail.com>
To: xen-devel@lists.xen.org
Subject: HVMLOADER test fails on AMD if CR3 write intercepts are enabled (XEN 4.4 stable)
Date: Sun, 27 Jul 2014 19:03:35 -0600 [thread overview]
Message-ID: <CAKuLJhBsPyo89hrO1EDcKG+rOvgwuwLkp1knfWt5Yzz5CFJq1g@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 987 bytes --]
Hi,
The HVMLOADER test fails on AMD SVM with Nested Paging enabled **Only**
when CR3 control registers write intercepts are enabled.
(By default the CR3 write intercepts are disabled on HAP domains)
The first test "rep_io" fails with the following output:
Bad value at 0x00500000: saw 98765432 expected 987654ff
Bad value at 0x00500ffc: saw 00000000 expected ff000000
Bad value at 0x00600000: saw 000000ff expected 00000000
Bad value at 0x00600ffc: saw ff000000 expected 00000000
The second test execution results in the triple fault.
The paging is setup as writing to va 0x600000 a value of 98765432 works
fine. (Since the test can see the same value at physical address 0x500000).
But after that the insb mov to address are not writing the memory correctly.
The only change made in the code is to enable CR3 intercepts on a similar
lines as done in VMX counterpart.
Seen in:
Xen 4.4 stable, AMD SVM with HAP
Can any one suggest what can be the issue behind this.
thanks.
[-- Attachment #1.2: Type: text/html, Size: 1804 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:[~2014-07-28 1:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 1:03 Abhiroop Dabral [this message]
2014-08-04 15:20 ` HVMLOADER test fails on AMD if CR3 write intercepts are enabled (XEN 4.4 stable) 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=CAKuLJhBsPyo89hrO1EDcKG+rOvgwuwLkp1knfWt5Yzz5CFJq1g@mail.gmail.com \
--to=abhiroop.dabral@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).