From: Gianluca Guida <gianluca.guida@eu.citrix.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH 4/4] Out-of-sync L1 shadows: Always unsync policy.
Date: Fri, 20 Jun 2008 18:32:22 +0100 [thread overview]
Message-ID: <485BE9A6.2040208@eu.citrix.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 115 bytes --]
Unsync policy: always unsync pages on guest writes.
Signed-off-by: Gianluca Guida <gianluca.guida@eu.citrix.com>
[-- Attachment #2: oos-policy.always.patch --]
[-- Type: text/x-patch, Size: 682 bytes --]
diff -r e1c198471d4d xen/arch/x86/mm/shadow/multi.c
--- a/xen/arch/x86/mm/shadow/multi.c Fri Jun 20 15:11:33 2008 +0100
+++ b/xen/arch/x86/mm/shadow/multi.c Fri Jun 20 15:12:27 2008 +0100
@@ -3288,6 +3288,13 @@ static int sh_page_fault(struct vcpu *v,
return 0;
}
+#if (SHADOW_OPTIMIZATIONS & SHOPT_OUT_OF_SYNC)
+ /* Always unsync when writing to L1 page tables. */
+ if ( sh_mfn_is_a_page_table(gmfn)
+ && ft == ft_demand_write )
+ sh_unsync(v, gmfn, va);
+#endif /* OOS */
+
/* Calculate the shadow entry and write it */
l1e_propagate_from_guest(v, gw.l1e, gmfn, &sl1e, ft, p2mt);
r = shadow_set_l1e(v, ptr_sl1e, sl1e, sl1mfn);
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2008-06-20 17:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=485BE9A6.2040208@eu.citrix.com \
--to=gianluca.guida@eu.citrix.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.