From: Dario Faggioli <dario.faggioli@citrix.com>
To: Daniel De Graaf <dgdegra@tycho.nsa.gov>
Cc: Marcus Granado <Marcus.Granado@eu.citrix.com>,
"andre.przywara@amd.com" <andre.przywara@amd.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"anil@recoil.org" <anil@recoil.org>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
"juergen.gross@ts.fujitsu.com" <juergen.gross@ts.fujitsu.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"JBeulich@suse.com" <JBeulich@suse.com>,
"msw@amazon.com" <msw@amazon.com>,
"Keir (Xen.org)" <keir@xen.org>
Subject: Re: [PATCH RFC] flask: move policy header sources into hypervisor
Date: Wed, 10 Oct 2012 15:39:48 +0100 [thread overview]
Message-ID: <1349879988.3610.194.camel@Abyss> (raw)
In-Reply-To: <50758038.6050009@tycho.nsa.gov>
[-- Attachment #1.1: Type: text/plain, Size: 2401 bytes --]
On Wed, 2012-10-10 at 15:03 +0100, Daniel De Graaf wrote:
> Ah, in my distraction with fixing the autogeneration I neglected to
> finish looking at the original patch.
>
:-)
> The XSM changes look good except
> for a missing implementation of the dummy_nodeaffinity() function in
> xen/xsm/dummy.c. However, since the implementation of xsm_nodeaffinity
> and xsm_vcpuaffinity are identical, it may be simpler to just merge them
> into a common xsm_affinity_domctl hook (as is implemented in
> xsm/flask/hooks.c) - in that case, just renaming the existing dummy hook
> will suffice.
>
Ok, thanks. I will do that.
> A more general note on the topic of what XSM permissions to use:
> normally, each domctl has its own permission, and so adding new domctls
> would be done by adding a new permission to the access_vectors file
> (which is the source of av_perm_to_string.h). However, for this case, it
> seems rather unlikely that one would want to allow access to vcpu
> affinity and deny node affinity, so using the same permission for both
> accesses is the best solution.
>
Yes, exactly.
Moreover, looking at xen/xsm/flask/include/av_permissions.h where
DOMAIN__{GET,SET}VCPUAFFINITY are, I got thee impression that there is
no more space left for DOMAIN__* permissions, as they already go from
0x00000001UL to 0x80000000UL... Is that so?
> When renaming a permission (such as getvcpuaffinity => getaffinity), the
> FLASK policy also needs to be changed - you can normally just grep for
> the permission being changed.
>
Ok and thanks again. I will do that too...
> The dummy hook would be caught in a compilation with XSM enabled, but I
> notice that current xen-unstable will not build due to a patch being
> applied out of order (xsm/flask: add domain relabel support requires
> rcu_lock_domain_by_any_id which was added in the prior patch). Adding
> Keir to CC since he applied the patch.
>
... As well as I will try to check for this for next round (hoping that
by that time the issue you're describing here would be fixed :-)).
Thanks a lot and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-10-10 14:39 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 14:08 [PATCH 0 of 8] NUMA Awareness for the Credit Scheduler Dario Faggioli
2012-10-05 14:08 ` [PATCH 1 of 8] xen, libxc: rename xenctl_cpumap to xenctl_bitmap Dario Faggioli
2012-10-09 15:59 ` George Dunlap
2012-10-05 14:08 ` [PATCH 2 of 8] xen, libxc: introduce node maps and masks Dario Faggioli
2012-10-09 15:59 ` George Dunlap
2012-10-05 14:08 ` [PATCH 3 of 8] xen: let the (credit) scheduler know about `node affinity` Dario Faggioli
2012-10-05 14:25 ` Jan Beulich
2012-10-09 10:29 ` Dario Faggioli
2012-10-09 11:10 ` Keir Fraser
2012-10-09 9:53 ` Juergen Gross
2012-10-09 10:21 ` Dario Faggioli
2012-10-09 16:29 ` George Dunlap
2012-10-05 14:08 ` [PATCH 4 of 8] xen: allow for explicitly specifying node-affinity Dario Faggioli
2012-10-09 16:47 ` George Dunlap
2012-10-09 16:52 ` Ian Campbell
2012-10-09 18:31 ` [PATCH RFC] flask: move policy header sources into hypervisor Daniel De Graaf
2012-10-10 8:38 ` Ian Campbell
2012-10-10 8:44 ` Dario Faggioli
2012-10-10 14:03 ` Daniel De Graaf
2012-10-10 14:39 ` Dario Faggioli [this message]
2012-10-10 15:32 ` Daniel De Graaf
2012-10-09 17:17 ` [PATCH 4 of 8] xen: allow for explicitly specifying node-affinity Dario Faggioli
2012-10-05 14:08 ` [PATCH 5 of 8] libxc: " Dario Faggioli
2012-10-05 14:08 ` [PATCH 6 of 8] libxl: " Dario Faggioli
2012-10-05 14:08 ` [PATCH 7 of 8] libxl: automatic placement deals with node-affinity Dario Faggioli
2012-10-10 10:55 ` George Dunlap
2012-10-05 14:08 ` [PATCH 8 of 8] xl: add node-affinity to the output of `xl list` Dario Faggioli
2012-10-05 16:36 ` Ian Jackson
2012-10-09 11:07 ` Dario Faggioli
2012-10-09 15:03 ` Ian Jackson
2012-10-10 8:46 ` Dario Faggioli
2012-10-08 19:43 ` [PATCH 0 of 8] NUMA Awareness for the Credit Scheduler Dan Magenheimer
2012-10-09 10:45 ` Dario Faggioli
2012-10-09 20:20 ` Matt Wilson
2012-10-10 16:18 ` Dario Faggioli
2012-10-09 10:02 ` Juergen Gross
2012-10-10 11:00 ` George Dunlap
2012-10-10 12:28 ` Dario Faggioli
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=1349879988.3610.194.camel@Abyss \
--to=dario.faggioli@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=Marcus.Granado@eu.citrix.com \
--cc=andre.przywara@amd.com \
--cc=anil@recoil.org \
--cc=dgdegra@tycho.nsa.gov \
--cc=juergen.gross@ts.fujitsu.com \
--cc=keir@xen.org \
--cc=msw@amazon.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).