[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [RFC] [PATCH] [XEN] [ACM] Enable updating policy on running system
- To: Stefan Berger <stefanb@xxxxxxxxxx>
- 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
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
- Thread-index: AceDa3frtkZ9v+9eEduiOwAX8io7RQ==
- Thread-topic: [Xen-devel] [RFC] [PATCH] [XEN] [ACM] Enable updating policy on running system
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
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
