All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Abhiroop Dabral <abhiroop.dabral@gmail.com>,
	boris.ostrovsky@oracle.com, suravee.suthikulpanit@amd.com,
	Aravind.Gopalakrishnan@amd.com
Cc: xen-devel@lists.xen.org
Subject: Re: HVMLOADER test fails on AMD if CR3 write intercepts are enabled (XEN 4.4 stable)
Date: Mon, 4 Aug 2014 11:20:08 -0400	[thread overview]
Message-ID: <20140804152008.GA20097@laptop.dumpdata.com> (raw)
In-Reply-To: <CAKuLJhBsPyo89hrO1EDcKG+rOvgwuwLkp1knfWt5Yzz5CFJq1g@mail.gmail.com>

On Sun, Jul 27, 2014 at 07:03:35PM -0600, Abhiroop Dabral wrote:
> Hi,

Hey,

Please use the MAINTAINERs file in the future to make sure that
the maintainers of the AMD SVM code can see this email. I've
done that for you.

> 
> 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)

How did you enable the cr3 interception? Was there an configuration
flag or was this something you modified in Xen?

> 
> 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.

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

      reply	other threads:[~2014-08-04 15:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-28  1:03 HVMLOADER test fails on AMD if CR3 write intercepts are enabled (XEN 4.4 stable) Abhiroop Dabral
2014-08-04 15:20 ` Konrad Rzeszutek Wilk [this message]

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=20140804152008.GA20097@laptop.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Aravind.Gopalakrishnan@amd.com \
    --cc=abhiroop.dabral@gmail.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=suravee.suthikulpanit@amd.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.