This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] [PATCH] [ACM] Support for removing / replacing a policy

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH] [ACM] Support for removing / replacing a policy
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Thu, 02 Aug 2007 13:36:23 -0400
Cc: Keir Fraser <keir@xxxxxxxxxxxxx>, sailer@xxxxxxxxxx
Delivery-date: Thu, 02 Aug 2007 10:26:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
This patch adds support for removing/replacing a policy from the running
system. This operation is only successful if currently running VMs would
also be allowed to run under the new policy. Removing the current policy
means that the default policy is installed, which then only has support
for a single VM label and STE type (SystemManagement) and is the same
policy that the system starts up with when no policy is chosen.

Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxx>

Attachment: acm_deactivate_policy.diff
Description: Text Data

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH] [ACM] Support for removing / replacing a policy, Stefan Berger <=