 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] xsm_op() polymorphism
| To: | "John Levon" <levon@xxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] xsm_op() polymorphism |
| From: | "George S. Coker, II" <george.coker@xxxxxxxxx> |
| Date: | Mon, 10 Dec 2007 19:05:03 -0500 |
| Cc: | xen-devel@xxxxxxxxxxxxxxxxxxx |
| Delivery-date: | Mon, 10 Dec 2007 16:05:48 -0800 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=oLA4Wy6/nJg3hFNBCOCIeqwz+nlZD48ScMS8+eq6mfc=; b=YDLaFlOzwTG00SCKaVxOqFcolkI8+RCsxy2sC/bJVfVO8n+GJQHyhI835IdxRUEW8KwLSlZBPwV+sedgopJOyvbvOdTpQvVBaV+Ro1xOBDpQRa7xgy6BwndztRcIdx95puPRcyC7pe5LoRMZ8Vuk/TOvQM0KXtIYbDPDzX3zl0A= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tFN0lpmELXsHMA9UISKD8VzRz9MGTMteSWR0Zgu27VuqGOMXMDnYfPu4Zr9mfWcXbs5V23/xR/4SxAA1cYLl/ylJx4MciDxZcNqWUQa1RzvjCVwoeZyQ1g6F0VfC8JPiMj6+EEJCVWAEeKc4yzkMp5YayVaBszx7U3EwQ8ipFaU= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| In-reply-to: | <20071210194122.GA4293@xxxxxxxxxxxxxxxxxxxxxxx> |
| 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> |
| References: | <20071210194122.GA4293@xxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
On Dec 10, 2007 2:41 PM, John Levon <levon@xxxxxxxxxxxxxxxxx> wrote: > > If I'm reading the code right, then the xsm_op() hypercall is "untyped" > in the sense that you have to know why XSM is loaded before you can > interpret any of the contents (that is, the first argument points > directly to a flask op or acm op structure). This seems less than ideal > - can't we work out a way to make the struct self-identifying? > It depends on what you are concerned about. There are the magic numbers that are used right now to identify policy modules on boot but could become embedded as the first word of the xsm op structure. This would help the hypervisor be consistent with user-space - if that's what you are concerned about. It was not the intent to make the hypervisor runtime agile wrt a given security module except to not prevent a security module from runtime disablement - for obvious reasons more flexibility here is fraught with consistency problems. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-devel] [PATCH] [DOCS] Adjust revision number in Xen-API document and introduce revision history., Stefan Berger |
|---|---|
| Next by Date: | Re: [Xen-devel] [FW: FYI: The plan for Xen kernels in Fedora 9], Chuck Short |
| Previous by Thread: | [Xen-devel] xsm_op() polymorphism, John Levon |
| Next by Thread: | Re: [Xen-devel] xsm_op() polymorphism, John Levon |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
