[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <53DA83B3.5050406@citrix.com>
Date: Thu, 31 Jul 2014 18:58:11 +0100
From: David Vrabel <david.vrabel@...rix.com>
To: George Dunlap <George.Dunlap@...citrix.com>
CC: Ian Campbell <Ian.Campbell@...rix.com>,
Frediano Ziglio <frediano.ziglio@...rix.com>,
xen-devel <xen-devel@...ts.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
<linux-api@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [Xen-devel] [PATCH 1/2] xen: Implement ioctl to restrict privcmd
to a specific domain
On 31/07/14 18:49, George Dunlap wrote:
> On Thu, Jul 31, 2014 at 10:11 AM, David Vrabel <david.vrabel@...rix.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists