Displaying 8 results from an estimated 8 matches for "ei_data".
Did you mean:
i_data
2009 Jan 14
5
[PATCH] Support cross-bitness guest when core-dumping
This patch allows core-dumping to work on a cross-bit host/guest configuration, whereas previously that was not supported. It supports both PV and FV guests. The core file format generated by the host, needs to match that of the guest, so an alignment issue is addressed, along with the p2m frame list handling being done according to the guest size.
Signed-off-by: Bruce Rogers
2008 Oct 20
0
PATCH[001/001]: mboot.c: prefer ELF header over multiboot header
...((load_size > sizeof(Elf32_Ehdr) &&
+ BOOTABLE_I386_ELF((*((Elf32_Ehdr *) load_addr))))) {
- /* Now look for an ELF32 header */
ehdr = (Elf32_Ehdr *)load_addr;
- if (*(unsigned long *)ehdr != 0x464c457f
- || ehdr->e_ident[EI_DATA] != ELFDATA2LSB
- || ehdr->e_ident[EI_CLASS] != ELFCLASS32
- || ehdr->e_machine != EM_386)
- {
- printf("Fatal: kernel has neither ELF32/x86 nor multiboot load"
- " headers.\n");
-...
2007 Mar 05
7
[PATCH 2/10] linux 2.6.18: COMPAT_VDSO
...+ unsigned long dynsym = 0;
+
+ BUG_ON(ehdr->e_ident[EI_MAG0] != ELFMAG0);
+ BUG_ON(ehdr->e_ident[EI_MAG1] != ELFMAG1);
+ BUG_ON(ehdr->e_ident[EI_MAG2] != ELFMAG2);
+ BUG_ON(ehdr->e_ident[EI_MAG3] != ELFMAG3);
+ BUG_ON(ehdr->e_ident[EI_CLASS] != ELFCLASS32);
+ BUG_ON(ehdr->e_ident[EI_DATA] != ELFDATA2LSB);
+ BUG_ON(ehdr->e_ehsize < sizeof(*ehdr));
+ ehdr->e_entry += new_base - old_base;
+ BUG_ON(ehdr->e_phentsize < sizeof(Elf32_Phdr));
+ for (i = 0; i < ehdr->e_phnum; ++i) {
+ Elf32_Phdr *phdr = (void *)((unsigned long)ehdr + ehdr->e_phoff + i * ehdr->e_p...
2007 Mar 05
7
[PATCH 2/10] linux 2.6.18: COMPAT_VDSO
...+ unsigned long dynsym = 0;
+
+ BUG_ON(ehdr->e_ident[EI_MAG0] != ELFMAG0);
+ BUG_ON(ehdr->e_ident[EI_MAG1] != ELFMAG1);
+ BUG_ON(ehdr->e_ident[EI_MAG2] != ELFMAG2);
+ BUG_ON(ehdr->e_ident[EI_MAG3] != ELFMAG3);
+ BUG_ON(ehdr->e_ident[EI_CLASS] != ELFCLASS32);
+ BUG_ON(ehdr->e_ident[EI_DATA] != ELFDATA2LSB);
+ BUG_ON(ehdr->e_ehsize < sizeof(*ehdr));
+ ehdr->e_entry += new_base - old_base;
+ BUG_ON(ehdr->e_phentsize < sizeof(Elf32_Phdr));
+ for (i = 0; i < ehdr->e_phnum; ++i) {
+ Elf32_Phdr *phdr = (void *)((unsigned long)ehdr + ehdr->e_phoff + i * ehdr->e_p...
2007 Mar 05
7
[PATCH 2/10] linux 2.6.18: COMPAT_VDSO
...+ unsigned long dynsym = 0;
+
+ BUG_ON(ehdr->e_ident[EI_MAG0] != ELFMAG0);
+ BUG_ON(ehdr->e_ident[EI_MAG1] != ELFMAG1);
+ BUG_ON(ehdr->e_ident[EI_MAG2] != ELFMAG2);
+ BUG_ON(ehdr->e_ident[EI_MAG3] != ELFMAG3);
+ BUG_ON(ehdr->e_ident[EI_CLASS] != ELFCLASS32);
+ BUG_ON(ehdr->e_ident[EI_DATA] != ELFDATA2LSB);
+ BUG_ON(ehdr->e_ehsize < sizeof(*ehdr));
+ ehdr->e_entry += new_base - old_base;
+ BUG_ON(ehdr->e_phentsize < sizeof(Elf32_Phdr));
+ for (i = 0; i < ehdr->e_phnum; ++i) {
+ Elf32_Phdr *phdr = (void *)((unsigned long)ehdr + ehdr->e_phoff + i * ehdr->e_p...
2007 Jan 18
13
[PATCH 0/5] dump-core take 2:
The following dump-core patches changes its format into ELF,
adds PFN-GMFN table, HVM support, and adds experimental IA64 support.
- ELF format
Program header and note section are adopted.
- HVM domain support
To know the memory area to dump, XENMEM_set_memory_map is added.
XENMEM_memory_map hypercall is for current domain, so new one is created.
and hvm domain builder tell xen its
2007 Jun 20
9
[PATCH 0/9] x86 boot protocol updates
[ This patch depends on the cross-architecture ELF cleanup patch. ]
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting. This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which
2007 Jun 20
9
[PATCH 0/9] x86 boot protocol updates
[ This patch depends on the cross-architecture ELF cleanup patch. ]
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting. This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which