All of lore.kernel.org
 help / color / mirror / Atom feed
From: jeet <jeet_sat12@yahoo.co.in>
To: Tim Deegan <Tim.Deegan@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: page fault handling in Xen
Date: Mon, 5 Mar 2007 11:59:18 +0530 (IST)	[thread overview]
Message-ID: <77764.294.qm@web8811.mail.in.yahoo.com> (raw)

Hi Tim

in case of second fault that will occur when guest will try to write in GPT(which is readonly)
and faulting address would be of Page table in which the write is attempted. VM exit will occur and xen would execute 
following code

in file  xen-3.0.3_0-src\xen\arch\mm\shadow\multi.c  in the page fault handler

static int sh_page_fault(struct vcpu *v, 
                          unsigned long va, 
                          struct cpu_user_regs *regs)
{
...
...
[line 2949]
  // Was it a write fault?
    //
    if ( regs->error_code & PFEC_write_access )
    {
    // //if error is write access and RW permission is not present
        if ( unlikely(!(accumulated_gflags & _PAGE_RW)) )
        {
             perfc_incrc(shadow_fault_bail_ro_mapping);
            goto not_a_shadow_fault;
        }

...
..

Above code will execute and in inner unlikely condition will be true as PT table is read only and  error is write_access
and control will go to not_a_shadow_fault?

so when the emulation code would be executed for the write that has been performed on read only guest PT for adding entry in 
guest page table by guest?

Have I missed some thing here in understanding 

kindly provide your valuable reply 

jeet

----- Original Message ----
From: Tim Deegan <Tim.Deegan@xensource.com>
To: jeet <jeet_sat12@yahoo.co.in>
Cc: xen-devel@lists.xensource.com
Sent: Friday, 2 March, 2007 7:05:43 PM
Subject: Re: [Xen-devel] page fault handling in Xen

At 17:36 +0530 on 02 Mar (1172856988), jeet wrote:
> Is shadow code implementation in xen 3.0.3 is same as explained by you in reply?

Yes.

Cheers,

Tim.

-- 
Tim Deegan <Tim.Deegan@xensource.com>, XenSource UK Limited
Registered office c/o EC2Y 5EB, UK; company number 05334508

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel





		
__________________________________________________________
Yahoo! India Answers: Share what you know. Learn something new
http://in.answers.yahoo.com/

             reply	other threads:[~2007-03-05  6:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-05  6:29 jeet [this message]
2007-03-05  8:19 ` page fault handling in Xen Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2007-03-06 13:16 jeet
2007-03-05 13:09 jeet
2007-03-05 13:21 ` Tim Deegan
2007-03-02 12:06 jeet
2007-03-02 13:35 ` Tim Deegan
2007-03-02  9:09 jeet
2007-03-02  9:36 ` Tim Deegan
2005-10-08 22:39 Jonathan M. McCune
2005-10-08 22:34 ` Keir Fraser

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=77764.294.qm@web8811.mail.in.yahoo.com \
    --to=jeet_sat12@yahoo.co.in \
    --cc=Tim.Deegan@xensource.com \
    --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.