From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [Xense-devel] [PATCH] [1/4] XSM Framework Date: Thu, 21 Dec 2006 10:53:50 +0000 Message-ID: References: <1166623720.4824.264.camel@moss-walleye.epoch.ncsc.mil> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1166623720.4824.264.camel@moss-walleye.epoch.ncsc.mil> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "George S. Coker, II" , xen-devel@lists.xensource.com, xense-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 20/12/06 14:08, "George S. Coker, II" wrote: > Modules may also define at Xen compile time a magic number XSM_MAGIC to > indicate that a policy should be discovered from the images loaded at > boot. The policy file should then be listed in grub as one of the > multi-boot modules after the dom0 kernel. ACM code is currently present in xen, xend and in the xm command-line tool. Do the XSM patches remove all this ACM-specific code, since (I believe) XSM logically subsumes ACM? -- Keir