 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] libelf.h and elfstructs.h
| To: | <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] libelf.h and elfstructs.h |
| From: | "Jan Beulich" <jbeulich@xxxxxxxxxx> |
| Date: | Mon, 22 Dec 2008 10:15:19 +0000 |
| Delivery-date: | Mon, 22 Dec 2008 02:15:14 -0800 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| 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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
What is the reason for these two to be part of the public (interface) headers? Using them anywhere outside of the Xen tree could easily conflict with the various other ELF headers used in different environments. Thanks, Jan _______________________________________________ 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] guest attempted write to read-only memory page., Tian, Kevin |
|---|---|
| Next by Date: | [Xen-devel] [PATCH] Quick path for PIO instructions which cut more than half of the expense, Xiang, Kai |
| Previous by Thread: | [Xen-devel] guest attempted write to read-only memory page., Tian, Kevin |
| Next by Thread: | Re: [Xen-devel] libelf.h and elfstructs.h, Keir Fraser |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
