From: David Vrabel <david.vrabel-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
To: George Dunlap <George.Dunlap-mvvWK6WmYclDPfheJLI6IQ@public.gmane.org>
Cc: Ian Campbell
<Ian.Campbell-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>,
Frediano Ziglio
<frediano.ziglio-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>,
xen-devel
<xen-devel-GuqFBffKawtpuQazS67q72D2FQJk+8+b@public.gmane.org>,
Boris Ostrovsky
<boris.ostrovsky-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 31/07/14 18:49, George Dunlap wrote:
> On Thu, Jul 31, 2014 at 10:11 AM, David Vrabel <david.vrabel-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org> 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
WARNING: multiple messages have this Message-ID (diff)
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: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1XCqEY-0005zn-RQ@lists.xen.org>
2014-07-31 13:53 ` [PATCH 1/2] xen: Implement ioctl to restrict privcmd to a specific domain Ian Campbell
[not found] ` <1406814787.10395.2.camel@kazak.uk.xensource.com>
2014-07-31 14:11 ` David Vrabel
[not found] ` <E1XCr4q-0007Nh-3J@lists.xen.org>
2014-07-31 14:43 ` Frediano Ziglio
[not found] ` <1406817823.6753.4.camel@hamster.uk.xensource.com>
2014-07-31 14:58 ` Ian Campbell
[not found] ` <E1XCr4p-0007Nh-Qu@lists.xen.org>
[not found] ` <E1XCr4p-0007Nh-Qu-GuqFBffKawuEi8DpZVb4nw@public.gmane.org>
2014-07-31 17:49 ` [Xen-devel] " George Dunlap
2014-07-31 17:49 ` George Dunlap
2014-07-31 17:58 ` David Vrabel
[not found] ` <CAFLBxZYnaeEGTbuU5QoKJOU62Ck9p_B53bjAd46Z7uVgOxXH8g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-31 17:58 ` David Vrabel [this message]
2014-07-31 17:58 ` [Xen-devel] " David Vrabel
2014-07-31 17:49 ` George Dunlap
[not found] <E1XCqEY-0005zn-V2@lists.xen.org>
[not found] ` <E1XCqEY-0005zn-V2-GuqFBffKawuEi8DpZVb4nw@public.gmane.org>
2014-08-01 8:27 ` [Xen-devel] " Jan Beulich
2014-08-01 8:27 ` Jan Beulich
[not found] ` <53DB6B8D02000078000284D3-tRfBTM6QL9aeHWOVceGJHFaTQe2KTcn/@public.gmane.org>
2014-08-01 13:44 ` Frediano Ziglio
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-sxgqhf6nn4dqt0dzr+alfa@public.gmane.org \
--cc=George.Dunlap-mvvWK6WmYclDPfheJLI6IQ@public.gmane.org \
--cc=Ian.Campbell-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org \
--cc=boris.ostrovsky-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=frediano.ziglio-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=xen-devel-GuqFBffKawtpuQazS67q72D2FQJk+8+b@public.gmane.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 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.