On Fri, 22 Jul 2005, linux-os (Dick Johnson) wrote:
> Seems to be readable and starts with 'ELF'. It's something the the 'C'
> runtime may library use to make syscalls to the kernel. Older libraries
> used interrupt 0x80, newer ones may use this. Roland McGrath has made
> patches to this segment
Really appreciate that, is roland mcgrath listening? what's his email ID?
On 7/23/05, linux-os (Dick Johnson) <[EMAIL PROTECTED]> wrote:
>
> On Fri, 22 Jul 2005, vamsi krishna wrote:
>
> > Hi,
> >
> >> It doesn't. The 32-bit machines never show 64 bit words in
> >> /proc/NN/maps. They don't
On Fri, 22 Jul 2005, vamsi krishna wrote:
> Hi,
>
>> It doesn't. The 32-bit machines never show 64 bit words in
>> /proc/NN/maps. They don't "know" how.
>>
>> b7fd6000-b7fd7000 rw-p b7fd6000 00:00 0
>> b7ff5000-b7ff6000 rw-p b7ff5000 00:00 0
>> bffe1000-bfff6000 rw-p bffe1000 00:00 0
Hi,
> It doesn't. The 32-bit machines never show 64 bit words in
> /proc/NN/maps. They don't "know" how.
>
> b7fd6000-b7fd7000 rw-p b7fd6000 00:00 0
> b7ff5000-b7ff6000 rw-p b7ff5000 00:00 0
> bffe1000-bfff6000 rw-p bffe1000 00:00 0 [stack]
> e000-f000 ---p 00:00 0
On Fri, 22 Jul 2005, vamsi krishna wrote:
> Hello,
>
>>
>> The location of the vsyscall page is different on 32 and 64 bit
>> machines. So 0xe000 is NOT the address you are looking for while
>> dealing with the 64 bit machine. Rather 0xff60 is the
>> correct location (on
Hello,
>
> The location of the vsyscall page is different on 32 and 64 bit
> machines. So 0xe000 is NOT the address you are looking for while
> dealing with the 64 bit machine. Rather 0xff60 is the
> correct location (on x86-64).
>
Both my process's are 32-bit process's, its just
To the best of my knowledge, It is the vsyscall page. The manner in
which system calls were implemented has changed from using the 80h
interrupt directly to using the vsyscall page (on the x86 arch). This
makes for better throughput while running frequently used system calls
which do not affect
>I found that every process running in this kernel version has a
>virtual address mapping in /proc//maps file as follows
><-->
>e000-000 ---p 00:00 0
Hello All,
Sorry to interrupt you.
I have been facing a wierd problem on same kernel version
(2.6.5-7.97.smp) but running on different machines 32-bit and 64-bit
(which can run 32-bit also).
I found that every process running in this kernel version has a
virtual address mapping in /proc//maps
Hello All,
Sorry to interrupt you.
I have been facing a wierd problem on same kernel version
(2.6.5-7.97.smp) but running on different machines 32-bit and 64-bit
(which can run 32-bit also).
I found that every process running in this kernel version has a
virtual address mapping in
I found that every process running in this kernel version has a
virtual address mapping in /proc/pid/maps file as follows
--
e000-000 ---p 00:00 0
To the best of my knowledge, It is the vsyscall page. The manner in
which system calls were implemented has changed from using the 80h
interrupt directly to using the vsyscall page (on the x86 arch). This
makes for better throughput while running frequently used system calls
which do not affect
Hello,
The location of the vsyscall page is different on 32 and 64 bit
machines. So 0xe000 is NOT the address you are looking for while
dealing with the 64 bit machine. Rather 0xff60 is the
correct location (on x86-64).
Both my process's are 32-bit process's, its just one
On Fri, 22 Jul 2005, vamsi krishna wrote:
Hello,
The location of the vsyscall page is different on 32 and 64 bit
machines. So 0xe000 is NOT the address you are looking for while
dealing with the 64 bit machine. Rather 0xff60 is the
correct location (on x86-64).
Both my
Hi,
It doesn't. The 32-bit machines never show 64 bit words in
/proc/NN/maps. They don't know how.
b7fd6000-b7fd7000 rw-p b7fd6000 00:00 0
b7ff5000-b7ff6000 rw-p b7ff5000 00:00 0
bffe1000-bfff6000 rw-p bffe1000 00:00 0 [stack]
e000-f000 ---p 00:00 0
On Fri, 22 Jul 2005, vamsi krishna wrote:
Hi,
It doesn't. The 32-bit machines never show 64 bit words in
/proc/NN/maps. They don't know how.
b7fd6000-b7fd7000 rw-p b7fd6000 00:00 0
b7ff5000-b7ff6000 rw-p b7ff5000 00:00 0
bffe1000-bfff6000 rw-p bffe1000 00:00 0 [stack]
Really appreciate that, is roland mcgrath listening? what's his email ID?
On 7/23/05, linux-os (Dick Johnson) [EMAIL PROTECTED] wrote:
On Fri, 22 Jul 2005, vamsi krishna wrote:
Hi,
It doesn't. The 32-bit machines never show 64 bit words in
/proc/NN/maps. They don't know how.
On Fri, 22 Jul 2005, linux-os (Dick Johnson) wrote:
Seems to be readable and starts with 'ELF'. It's something the the 'C'
runtime may library use to make syscalls to the kernel. Older libraries
used interrupt 0x80, newer ones may use this. Roland McGrath has made
patches to this segment so
18 matches
Mail list logo
