All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emre Can Sezer <ecsezer@ncsu.edu>
To: Xen Devel <xen-devel@lists.xensource.com>
Subject: Re: Two shadow page tables for HVM
Date: Fri, 30 Jan 2009 11:15:01 -0500	[thread overview]
Message-ID: <49832785.3010809@ncsu.edu> (raw)
In-Reply-To: <20090127103413.GB990@york.uk.xensource.com>



>>  I'm using 64-bit PT's and as far as I
>> can tell EFER.NXE is turned on.  At least cpu_has_nx returns true and
>> that I get page faults with PFEC_instr_fetch error with both paging modes.
>>
>> Here is the summary of page fault errors:
>> ...
>> (XEN) sh_page_fault: d:v=1:0 va=0xffffffffa000f050 err=17,
>> rip=ffffffffa000f050
>> (XEN) <ECS> Switching to ALTERNATE paging mode
>> (XEN) <ECS-alt> sh_page_fault: d:v=1:0 va=0xffffffff8062cef0 err=0,
>> rip=ffffffffa000f050
>> (XEN) <ECS-alt> sh_page_fault: d:v=1:0 va=0xffffffff805d8010 err=0,
>> rip=ffffffffa000f050
>> (XEN) <ECS-alt> sh_page_fault: d:v=1:0 va=0xffffffff8020cea0 err=10,
>> rip=ffffffff8020cea0
>> (XEN) <ECS> Switching to NORMAL paging mode
>> (XEN) <ECS> Done
>> ...
>>
>> I'm also confused about the last page fault.  No page fault occurred
>> that propagated this page's pte from the guest (I turned off
>> prefetching). I'm inclined to think that I have some artifacts from the
>> initial paging mode.
>>     
>
> Seems like a fair explanation. 
>   
The intel software development manual states:
P flag = 0 --> PF due to page not present
P flag = 1 --> PF due to protection violation

If this flag is used as it is, it would explain the error code being 0.

I'm looking into why there isn't another instruction fetch.

John





>   

      parent reply	other threads:[~2009-01-30 16:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 23:06 Two shadow page tables for HVM Emre Can Sezer
2008-12-18  3:50 ` Sina Bahram
2008-12-18 11:32 ` Tim Deegan
2008-12-22 18:28   ` Emre Can Sezer
2008-12-23 12:03     ` Gianluca Guida
     [not found]   ` <494FC8C7.8030508@ncsu.edu>
     [not found]     ` <20081223161006.GB28336@york.uk.xensource.com>
2008-12-29 16:17       ` Emre Can Sezer
     [not found]       ` <4958F7E0.8050207@ncsu.edu>
     [not found]         ` <20081229165415.GB5734@york.uk.xensource.com>
2009-01-09 22:08           ` Emre Can Sezer
2009-01-12  9:46             ` Tim Deegan
2009-01-27  0:39               ` Emre Can Sezer
2009-01-27 10:34                 ` Tim Deegan
2009-01-27 19:07                   ` Emre Can Sezer
2009-01-28  9:25                     ` Tim Deegan
2009-01-30 16:15                   ` Emre Can Sezer [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=49832785.3010809@ncsu.edu \
    --to=ecsezer@ncsu.edu \
    --cc=xen-devel@lists.xensource.com \
    /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.