search for: _bss

...eturn milisecs()/1000;}; mov ecx, DWORD PTR _tfim sub ecx, DWORD PTR _tini mov eax, 274877907 ; 10624dd3H mul ecx shr edx, 6 mov eax, edx ret 0 _secs ENDP _TEXT ENDS PUBLIC ??_C at _0BE@FFMOMMDD@?$CF02d?3?$CF02d?3?$CF02d?3?$CF03d?$AA@ ; `string' PUBLIC _spenttime EXTRN _sprintf:PROC _BSS SEGMENT ?buffer@?1??spenttime@@9 at 9 DB 040H DUP (?) ; `spenttime'::`2'::buffer _BSS ENDS ; COMDAT ??_C at _0BE@FFMOMMDD@?$CF02d?3?$CF02d?3?$CF02d?3?$CF03d?$AA@ CONST SEGMENT ??_C at _0BE@FFMOMMDD@?$CF02d?3?$CF02d?3?$CF02d?3?$CF03d?$AA@ DB '%02d:%02d:' DB '%02d:%03d', 00H...

...(startup_32) SECTIONS { - /* Be careful parts of head.S assume startup_32 is at - * address 0. - */ . = 0 ; .text.head : { + *(.elfhdr) _head = . ; *(.text.head) _ehead = . ; @@ -33,6 +32,7 @@ SECTIONS *(.data.*) _edata = . ; } + _filesz = . ; .bss : { _bss = . ; *(.bss) @@ -40,4 +40,11 @@ SECTIONS *(COMMON) _end = . ; } + _memsz = .; + + .notes : { + _notes = . ; + *(.note*) + _notesz = . - _notes ; + } } =================================================================== --- a/arch/i386/boot/compressed/vmlinux.scr +++ /dev/null @@ -1,...

...(startup_32) SECTIONS { - /* Be careful parts of head.S assume startup_32 is at - * address 0. - */ . = 0 ; .text.head : { + *(.elfhdr) _head = . ; *(.text.head) _ehead = . ; @@ -33,6 +32,7 @@ SECTIONS *(.data.*) _edata = . ; } + _filesz = . ; .bss : { _bss = . ; *(.bss) @@ -40,4 +40,11 @@ SECTIONS *(COMMON) _end = . ; } + _memsz = .; + + .notes : { + _notes = . ; + *(.note*) + _notesz = . - _notes ; + } } =================================================================== --- a/arch/i386/boot/compressed/vmlinux.scr +++ /dev/null @@ -1,...

[ 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

[ 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

This series: 1. Updates the boot protocol to version 2.07 2. Clean up the existing build process, to get rid of tools/build and make the linker do more heavy lifting 3. Make the bzImage payload an ELF file. The bootloader can extract this as a naked ELF file by skipping over boot_params.setup_sects worth of 16-bit setup code. 4. Update the boot_params to 2.07, and update the

This series: 1. Updates the boot protocol to version 2.07 2. Clean up the existing build process, to get rid of tools/build and make the linker do more heavy lifting 3. Make the bzImage payload an ELF file. The bootloader can extract this as a naked ELF file by skipping over boot_params.setup_sects worth of 16-bit setup code. 4. Update the boot_params to 2.07, and update the

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 adds fields to specify the hardware subarchitecture and some

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 adds fields to specify the hardware subarchitecture and some

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 adds fields to specify the hardware subarchitecture and some