 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] CONFIG_COMPAT
| To: | xen-devel@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [Xen-devel] CONFIG_COMPAT |
| From: | Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> |
| Date: | Thu, 7 Feb 2008 13:30:01 +0000 |
| Delivery-date: | Thu, 07 Feb 2008 05:32:25 -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 |
What is the purpose of CONFIG_COMPAT ? It seems to be enabled precisely in 64-bit hypervisors and not otherwise, and is related to support of 32-bit guests including dom0. Is there some reason why this needs to be configurable separately from 64bitness ? Ian. _______________________________________________ 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] fix initialisation of physaddr_bitsize etc., Ian Jackson |
|---|---|
| Next by Date: | [Xen-devel] save/restore pass-through enabled domU, Masroor Vettuparambil |
| Previous by Thread: | [Xen-devel] [PATCH] fix initialisation of physaddr_bitsize etc., Ian Jackson |
| Next by Thread: | Re: [Xen-devel] CONFIG_COMPAT, Jan Beulich |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
