From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Tim Deegan <tim@xen.org>, "Tian, Kevin" <kevin.tian@intel.com>
Cc: "Yu, Zhang" <yu.c.zhang@linux.intel.com>,
"Paul.Durrant@citrix.com" <Paul.Durrant@citrix.com>,
"keir@xen.org" <keir@xen.org>,
"JBeulich@suse.com" <JBeulich@suse.com>,
"Xen-devel@lists.xen.org" <Xen-devel@lists.xen.org>
Subject: Re: One question about the hypercall to translate gfn to mfn.
Date: Thu, 18 Dec 2014 17:01:28 +0000 [thread overview]
Message-ID: <54930868.7060603@citrix.com> (raw)
In-Reply-To: <20141218160846.GD67264@deinos.phlegethon.org>
On 18/12/14 16:08, Tim Deegan wrote:
>> yep. Just curious, I thought stubdomain is not popularly used. typical
>> > case is to have qemu in dom0. is this still true? :-)
> Some do and some don't. :) High-security distros like Qubes and
> XenClient do. You can enable it in xl config files pretty easily.
> IIRC the xapi toolstack doesn't use it, but XenServer uses privilege
> separation to isolate the qemu processes in dom0.
>
We are looking into stubdomains as part of future architectural roadmap,
but as identified, there is a lot of toolstack plumbing required before
this be feasible to put into XenServer.
Our privilege separate in qemu is a stopgap measure which we would like
to replace in due course.
~Andrew
next prev parent reply other threads:[~2014-12-18 17:01 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 10:10 One question about the hypercall to translate gfn to mfn Yu, Zhang
2014-12-09 10:19 ` Paul Durrant
2014-12-09 10:37 ` Yu, Zhang
2014-12-09 10:50 ` Jan Beulich
2014-12-10 1:07 ` Tian, Kevin
2014-12-10 8:39 ` Jan Beulich
2014-12-10 8:47 ` Tian, Kevin
2014-12-10 9:16 ` Jan Beulich
2014-12-10 9:51 ` Tian, Kevin
2014-12-10 10:07 ` Jan Beulich
2014-12-10 11:04 ` Malcolm Crossley
2014-12-10 8:50 ` Tian, Kevin
2014-12-09 10:51 ` Malcolm Crossley
2014-12-10 1:22 ` Tian, Kevin
2014-12-09 10:38 ` Jan Beulich
2014-12-09 10:46 ` Tim Deegan
2014-12-09 11:05 ` Paul Durrant
2014-12-09 11:11 ` Ian Campbell
2014-12-09 11:17 ` Paul Durrant
2014-12-09 11:23 ` Jan Beulich
2014-12-09 11:28 ` Malcolm Crossley
2014-12-09 11:29 ` Ian Campbell
2014-12-09 11:43 ` Paul Durrant
2014-12-10 1:48 ` Tian, Kevin
2014-12-10 10:11 ` Ian Campbell
2014-12-11 1:50 ` Tian, Kevin
2014-12-10 1:14 ` Tian, Kevin
2014-12-10 10:36 ` Jan Beulich
2014-12-11 1:45 ` Tian, Kevin
2014-12-10 10:55 ` Tim Deegan
2014-12-11 1:41 ` Tian, Kevin
2014-12-11 16:46 ` Tim Deegan
2014-12-12 7:24 ` Tian, Kevin
2014-12-12 10:54 ` Jan Beulich
2014-12-15 6:25 ` Tian, Kevin
2014-12-15 8:44 ` Jan Beulich
2014-12-15 9:05 ` Tian, Kevin
2014-12-15 9:22 ` Jan Beulich
2014-12-15 11:16 ` Tian, Kevin
2014-12-15 11:27 ` Jan Beulich
2014-12-15 15:22 ` Stefano Stabellini
2014-12-15 16:01 ` Jan Beulich
2014-12-15 16:15 ` Stefano Stabellini
2014-12-15 16:28 ` David Vrabel
2014-12-15 16:28 ` Jan Beulich
2014-12-18 15:46 ` Tim Deegan
2015-01-06 8:56 ` Tian, Kevin
2015-01-08 12:43 ` Tim Deegan
2015-01-09 8:02 ` Tian, Kevin
2015-01-09 20:08 ` Konrad Rzeszutek Wilk
2015-01-12 11:14 ` David Vrabel
2014-12-11 21:29 ` Tim Deegan
2014-12-12 6:29 ` Tian, Kevin
2014-12-18 16:08 ` Tim Deegan
2014-12-18 17:01 ` Andrew Cooper [this message]
2015-01-05 15:49 ` George Dunlap
2015-01-06 8:42 ` Tian, Kevin
2015-01-06 10:35 ` Ian Campbell
2014-12-12 7:30 ` Tian, Kevin
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=54930868.7060603@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=Xen-devel@lists.xen.org \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=tim@xen.org \
--cc=yu.c.zhang@linux.intel.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.