 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] xsm_op() polymorphism
| To: | xen-devel@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [Xen-devel] xsm_op() polymorphism |
| From: | John Levon <levon@xxxxxxxxxxxxxxxxx> |
| Date: | Mon, 10 Dec 2007 19:41:22 +0000 |
| Delivery-date: | Mon, 10 Dec 2007 11:42:40 -0800 |
| 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 |
| User-agent: | Mutt/1.5.9i |
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? thanks john _______________________________________________ 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] Xen Summit #5 Presentations and Abstracts on-line at xen.org, Ian Pratt |
|---|---|
| Next by Date: | RE: [Xen-devel] c-state support - anyone working on this?, Langsdorf, Mark |
| Previous by Thread: | [Xen-devel] Xen Summit #5 Presentations and Abstracts on-line at xen.org, Ian Pratt |
| Next by Thread: | Re: [Xen-devel] xsm_op() polymorphism, George S. Coker, II |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
