 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] hap_domctl
| To: | xen-devel@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [Xen-devel] hap_domctl |
| From: | John Levon <levon@xxxxxxxxxxxxxxxxx> |
| Date: | Tue, 24 Apr 2007 00:59:29 +0100 |
| Delivery-date: | Mon, 23 Apr 2007 16:53:42 -0700 |
| 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 |
494 int hap_domctl(struct domain *d, xen_domctl_shadow_op_t *sc,
495 XEN_GUEST_HANDLE(void) u_domctl)
513 case XEN_DOMCTL_SHADOW_OP_ENABLE:
514 HAP_ERROR("Bad hap domctl op %u\n", sc->op);
515 domain_crash(d);
516 return -EINVAL;
Line 515 looks very peculiar to me. Why are we punishing a domU for a
mistake in dom0?
regards
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: | Re: [Xen-devel] host CPU features/flags in xen API, Ewan Mellor |
|---|---|
| Next by Date: | Re: [Xen-devel] host CPU features/flags in xen API, John Levon |
| Previous by Thread: | [Xen-devel] host CPU features/flags in xen API, John Levon |
| Next by Thread: | Re: [Xen-devel] hap_domctl, Keir Fraser |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
