From: jeet <jeet_sat12@yahoo.co.in>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
Tim Deegan <Tim.Deegan@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: page fault handling in Xen
Date: Tue, 6 Mar 2007 18:46:17 +0530 (IST) [thread overview]
Message-ID: <247205.9650.qm@web8815.mail.in.yahoo.com> (raw)
>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
| Yes: guest PTs are mapped with write permissions in the guest PTs. It's only
| in the shadow PTs that the guest PTs are mapped read-only. The test on
| accumulated_gflags is looking at the access permissions in the guest PTs.
|
| -- Keir
Does this mean that on every new entry in level 4 guest page table will cause recursive page faults
to create all the entries from level 4 till level 1 shadow page table?
Jeet
_______________________________________________
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/
next reply other threads:[~2007-03-06 13:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 13:16 jeet [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-05 13:09 page fault handling in Xen jeet
2007-03-05 13:21 ` Tim Deegan
2007-03-05 6:29 jeet
2007-03-05 8:19 ` Keir Fraser
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=247205.9650.qm@web8815.mail.in.yahoo.com \
--to=jeet_sat12@yahoo.co.in \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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.