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


Re: [Xen-devel] [RFC] [PATCH] [XEN] [ACM] Enable updating policy on runn

To: Stefan Berger <stefanb@xxxxxxxxxx>
Subject: Re: [Xen-devel] [RFC] [PATCH] [XEN] [ACM] Enable updating policy on running system
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Fri, 20 Apr 2007 17:46:40 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 20 Apr 2007 09:45:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <OFF73A2046.DB192AB3-ON852572C3.00559620-852572C3.0058174A@xxxxxxxxxx>
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
Thread-index: AceDa3frtkZ9v+9eEduiOwAX8io7RQ==
Thread-topic: [Xen-devel] [RFC] [PATCH] [XEN] [ACM] Enable updating policy on running system
User-agent: Microsoft-Entourage/
On 20/4/07 17:02, "Stefan Berger" <stefanb@xxxxxxxxxx> wrote:

> Anyway, in response to your main question, I wonder what you actually need
> to serialise against? Is it sufficient to just sync against domain creation
> -- what if event channels or grant mappings are also occurring during the
> policy change? Is there some specific part of domain creation you need to
> serialise against?

While the policy update is happening, a domain could be created with a label that is about to be modified or even deleted as part of the policy update.

When a label is associated with a domain, doesn’t that call into ACM code? In which case you could define your own locking against that event.

 -- Keir
Xen-devel mailing list