List Info

Thread: Re: amd64 kernels and text address




Re: amd64 kernels and text address
country flaguser name
Germany
2008-03-26 08:40:44
On Mon, Mar 24, 2008 at 01:09:40PM +0100, Julio M. Merino
Vidal wrote:
> Upon further inspection, I noticed the following in the
resulting  
> binaries:
> 
> Idx Name          Size      VMA               LMA      
        File  
> off  Algn
>   0 .text         005c4548  ffffffff80100000 
ffffffff80100000   
> 00100000  2**6
>                   CONTENTS, ALLOC, LOAD, READONLY,
CODE

Not that I could offer any help, but just note that sparc64
has similar
constraints (needs text + rodata merged and big-page
aligned, puts data
big-page aligned after that), and it works there:

Idx Name          Size      VMA               LMA           
   File off  Algn
  0 .text         00230100  0000000001000000 
0000000001000000  00000100  2**7
                  CONTENTS, ALLOC, LOAD, READONLY, CODE

One other note: the leading zeros should not realy hurt that
much, as the
file is sparse, and all zeroes should compress pretty well.

How did you try to add your separate section?

Martin

Re: amd64 kernels and text address
country flaguser name
Spain
2008-03-26 15:27:31
On Mar 26, 2008, at 14:40 , Martin Husemann wrote:

> On Mon, Mar 24, 2008 at 01:09:40PM +0100, Julio M.
Merino Vidal wrote:
>> Upon further inspection, I noticed the following in
the resulting
>> binaries:
>>
>> Idx Name          Size      VMA               LMA  
            File
>> off  Algn
>>   0 .text         005c4548  ffffffff80100000 
ffffffff80100000
>> 00100000  2**6
>>                   CONTENTS, ALLOC, LOAD, READONLY,
CODE
>
> Not that I could offer any help, but just note that
sparc64 has  
> similar
> constraints (needs text + rodata merged and big-page
aligned, puts  
> data
> big-page aligned after that), and it works there:
>
> Idx Name          Size      VMA               LMA      
         
> File off  Algn
>   0 .text         00230100  0000000001000000 
0000000001000000   
> 00000100  2**7
>                   CONTENTS, ALLOC, LOAD, READONLY,
CODE
>
> One other note: the leading zeros should not realy hurt
that much,  
> as the
> file is sparse, and all zeroes should compress pretty
well.
>
> How did you try to add your separate section?

I added a

     .section "foo"
     <multiboot header contents>

in locore.S and then added

     .foo : { *(.foo) }

in the linker script, before .text.  I also tried with an
allocatable  
section.

Was that correct?

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )