From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: xen-devel@lists.xensource.com
Subject: [RFC] MM: stub domains and page ownership for mapping in dom0
Date: Thu, 6 Mar 2008 18:52:17 +0000 [thread overview]
Message-ID: <20080306185217.GC10848@implementation.uk.xensource.com> (raw)
In the case of an ioemu stubdomain with SDL or vnc server running in
dom0, we want to have the stubdomain expose the HVM guest's video RAM
through PVFB.
However, to map the pages from dom0, xenfb uses xc_map_foreign_pages
with the stubdomain ID as domid (since that is what is advertised in
the PVFB protocol, and needed for other parts of the protocol), and
thus get_page_from_l1e() complains because the stubdomain is not the
owner of the pages. In such case, this patch checks that the stubdomain
has privileges on the actual owner of the pages, and then accept the
mapping.
Any red flag?
Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com>
diff -r fb74347d80c3 xen/arch/x86/mm.c
--- a/xen/arch/x86/mm.c Wed Mar 05 12:20:40 2008 +0000
+++ b/xen/arch/x86/mm.c Thu Mar 06 18:35:55 2008 +0000
@@ -673,6 +673,14 @@ get_page_from_l1e
return 1;
}
+ /* Let privileged domains transfer the right to map their target domain's
+ * pages */
+ {
+ struct domain *owner = page_get_owner(page);
+ if (d != owner && IS_PRIV_FOR(d, owner))
+ d = owner;
+ }
+
/* Foreign mappings into guests in shadow external mode don't
* contribute to writeable mapping refcounts. (This allows the
* qemu-dm helper process in dom0 to map the domain's memory without
next reply other threads:[~2008-03-06 18:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 18:52 Samuel Thibault [this message]
2008-03-17 10:53 ` [RFC] MM: stub domains and page ownership for mapping in dom0 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=20080306185217.GC10848@implementation.uk.xensource.com \
--to=samuel.thibault@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.