[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [MINI-OS PATCH 03/12] add elf.h
On 21.03.2025 16:53, Jürgen Groß wrote: > On 21.03.25 14:51, Jan Beulich wrote: >> On 21.03.2025 10:24, Juergen Gross wrote: >>> +/* e_type */ >>> +#define ET_NONE 0 /* No file type */ >>> +#define ET_REL 1 /* relocatable file */ >>> +#define ET_EXEC 2 /* executable file */ >>> +#define ET_DYN 3 /* shared object file */ >>> +#define ET_CORE 4 /* core file */ >>> +#define ET_NUM 5 /* number of types */ >>> +#define ET_LOPROC 0xff00 /* reserved range for processor */ >>> +#define ET_HIPROC 0xffff /* specific e_type */ >>> + >>> +/* e_machine */ >>> +#define EM_NONE 0 /* No Machine */ >>> +#define EM_M32 1 /* AT&T WE 32100 */ >>> +#define EM_SPARC 2 /* SPARC */ >>> +#define EM_386 3 /* Intel 80386 */ >>> +#define EM_68K 4 /* Motorola 68000 */ >>> +#define EM_88K 5 /* Motorola 88000 */ >>> +#define EM_486 6 /* Intel 80486 - unused? */ >>> +#define EM_860 7 /* Intel 80860 */ >>> +#define EM_MIPS 8 /* MIPS R3000 Big-Endian only */ >>> +/* >>> + * Don't know if EM_MIPS_RS4_BE, >>> + * EM_SPARC64, EM_PARISC, >>> + * or EM_PPC are ABI compliant >>> + */ >>> +#define EM_MIPS_RS4_BE 10 /* MIPS R4000 Big-Endian */ >>> +#define EM_SPARC64 11 /* SPARC v9 64-bit unoffical */ >>> +#define EM_PARISC 15 /* HPPA */ >>> +#define EM_SPARC32PLUS 18 /* Enhanced instruction set SPARC */ >>> +#define EM_PPC 20 /* PowerPC */ >>> +#define EM_PPC64 21 /* PowerPC 64-bit */ >>> +#define EM_ARM 40 /* Advanced RISC Machines ARM */ >>> +#define EM_ALPHA 41 /* DEC ALPHA */ >>> +#define EM_SPARCV9 43 /* SPARC version 9 */ >>> +#define EM_ALPHA_EXP 0x9026 /* DEC ALPHA */ >>> +#define EM_IA_64 50 /* Intel Merced */ >>> +#define EM_X86_64 62 /* AMD x86-64 architecture */ >>> +#define EM_VAX 75 /* DEC VAX */ >>> +#define EM_AARCH64 183 /* ARM 64-bit */ >> >> Here I similarly think some stripping down might help. Doing so would then >> also permit to leave out the comment in the middle. > > Here I'm a little bit more on the edge. Some historical entries can > probably be dropped, but which ones would want to stay? The ones we presently need for any of the architectures we have (partial) ports for in the hypervisor, or that the hypervisor targets for compatibility. Jan
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |