search for: filesiz

...significantly larger than what would get with ld.gold or ld.bfd. # readelf -l test.bfd Elf file type is EXEC (Executable file) Entry point 0x4000b0 There are 2 program headers, starting at offset 64 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flags Align LOAD 0x0000000000000000 0x0000000000400000 0x0000000000400000 0x00000000000000c0 0x00000000000000c0 R E 0x200000 GNU_STACK 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000...

...from the resulting binary (and what ld.bfd produces) is that no ELF headers are allocated in the address space, e.g. Elf file type is EXEC (Executable file) Entry point 0x80001a0f There are 1 program headers, starting at offset 52 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x001000 0x80000000 0x80000000 0x08284 0x08284 RWE 0x1000 Section to Segment mapping: Segment Sections... 00 .text .rodata .eh_frame .data However, what ldd does is different. (To create a single segment I use --omagic argument, it works fine and is u...

...R RE R RW), and since we do not align sections to the page boundary manually or in script, it will not work I think. Below is lld output of FreeBSD kernel (notice that RE and R loads are not aligned): Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flags Align PHDR 0x0000000000000040 0xffffffff80001040 0xffffffff80001040 0x00000000000001f8 0x00000000000001f8 R 8 INTERP 0x0000000000000238 0xffffffff80001238 0xffffffff80001238 0x000000000000000d 0x0000...

...binutils, I get: $ readelf -l usr/klibc/libc.so Elf file type is EXEC (Executable file) Entry point 0x200200 There are 3 program headers, starting at offset 64 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flags Align LOAD 0x0000000000000000 0x0000000000200000 0x0000000000200000 0x0000000000011a5e 0x0000000000011a5e R E 200000 LOAD 0x0000000000011a60 0x0000000000411a60 0x0000000000411a60 0x0000000000000100 0...

I re-wrote the compile script to build klibc (cleaning up how I do it, and how to find the source tarballs). It seems to be compiling fine. I tried several of the commands in usr/utils/static and most one. However, the sleep command fails in a strange way (EINVAL on execve): ================================================================ faraday/phil /home/phil/klibc-project-0 581> strace

Hi, I hope I''m right here. If not then please point me in the right direction. My problem in short: I have problems using (pinning, mmu_update) physical pages from 0x900000 to 0xB1000 usualy. I''m writing my own little amd64 64bit toy kernel (based on Mini-OS as starting point) for xen and I run into problems with the way the start of day sets up the physical pages. My kernel

xc_dom_alloc_page deals with virtual address not physical address. When an ELF is loaded, virtual address and physical address may be different. Signed-off-by: Julien Grall <julien.grall@linaro.org> --- tools/libxc/xc_dom_arm.c | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/tools/libxc/xc_dom_arm.c b/tools/libxc/xc_dom_arm.c index a40e04d..75a6f1c

I've updated the patches at http://ozlabs.org/~rusty/paravirt/?mf=33ba6c4fce13;path=/ to carve out the basic shape of how I see all this fitting together. These patches implement an initial set of Xen paravirt ops, as well as adapting head.S to set up a Xen-specific entrypoint. The head.S code does absolutely minimal setup, and then calls xen_start_kernel(). This installs the Xen