From: Gianluca Guida <gianluca.guida@eu.citrix.com>
To: Emre Can Sezer <ecsezer@ncsu.edu>
Cc: Xen Devel <xen-devel@lists.xensource.com>
Subject: Re: Two shadow page tables for HVM
Date: Tue, 23 Dec 2008 13:03:02 +0100 [thread overview]
Message-ID: <4950D376.5000802@eu.citrix.com> (raw)
In-Reply-To: <494FDC38.7040400@ncsu.edu>
Emre Can Sezer wrote:
> Wouldn't this mean that the two page tables are NOT synchronized? When
> we switch paging modes, wouldn't we have to rebuild the entire shadow
> page tables from guest?
No. When updating shadows from guest, the shadow code will update the
changes for each existing shadow of the page.
> When considering the performance penalties of flushing the kernel page
> tables from the TLB, how significant is traversing all the shadow page
> tables for the guest kernel and updating their permissions? If there
> isn't an order of magnitude of difference, it might be reasonable to
> take the short cut in implementation.
It's up to the permission you're updating and how widely you want these
permissions applied. If (e.g. NX bit) one bit in the upper level set
permission for the whole part of the tree it maps, then you can just
change permissions on the top level shadows. Be sure, though, to cope
with the fault you get correctly.
Gianluca
next prev parent reply other threads:[~2008-12-23 12:03 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 [this message]
[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
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=4950D376.5000802@eu.citrix.com \
--to=gianluca.guida@eu.citrix.com \
--cc=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.