From: David Vrabel <david.vrabel@citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
Frediano Ziglio <frediano.ziglio@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
<linux-api@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH 1/2] xen: Implement ioctl to restrict privcmd to a specific domain
Date: Thu, 31 Jul 2014 18:58:11 +0100 [thread overview]
Message-ID: <53DA83B3.5050406@citrix.com> (raw)
In-Reply-To: <CAFLBxZYnaeEGTbuU5QoKJOU62Ck9p_B53bjAd46Z7uVgOxXH8g@mail.gmail.com>
On 31/07/14 18:49, George Dunlap wrote:
> On Thu, Jul 31, 2014 at 10:11 AM, David Vrabel <david.vrabel@citrix.com> wrote:
>> On 31/07/14 14:53, Ian Campbell wrote:
>>> On Thu, 2014-07-31 at 14:16 +0100, Frediano Ziglio wrote:
>>>
>>>> include/xen/interface/domctl.h | 1090 ++++++++++++++++++++++++++++++++++++
>>>
>>> domctl is an stable toolstack only hypervisor interface, so the kernel
>>> cannot use it because it would then break.
>>
>> Ok. I guess we'll have to resurrect the idea to do something with XSM.
>
> What kind of thing did you have in mind for XSM?
A multicall-like hypercall that has an additional parameter for a handle
to a XSM context to use for the contained hypercalls.
> In general it seems like allowing a vcpu to switch into an XSM label
> (not sure I've got the terminology right here) when it context
> switches into a particular process might be the most flexible way for
> that to work.
I think we want something than can a different policy on a per-fd basis.
David
next prev parent reply other threads:[~2014-07-31 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1XCqEY-0005zn-RQ@lists.xen.org>
[not found] ` <1406814787.10395.2.camel@kazak.uk.xensource.com>
[not found] ` <E1XCr4p-0007Nh-Qu@lists.xen.org>
2014-07-31 17:49 ` [Xen-devel] [PATCH 1/2] xen: Implement ioctl to restrict privcmd to a specific domain George Dunlap
2014-07-31 17:58 ` David Vrabel [this message]
[not found] <E1XCqEY-0005zn-V2@lists.xen.org>
2014-08-01 8:27 ` Jan Beulich
2014-08-01 13:44 ` Frediano Ziglio
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=53DA83B3.5050406@citrix.com \
--to=david.vrabel@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=frediano.ziglio@citrix.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox