[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensolaris-brandz-discuss
Subject:    [brandz-discuss] Linux vsyscall support on X64
From:       "Wei Shen" <cquark () gmail ! com>
Date:       2008-04-30 10:34:21
Message-ID: e12e59640804300334t58c1d8d0n1a0cf6920474ce50 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi all,

I meet some difficulty to add support for Linux vsyscall in lx64 brand.

Linux kernel (2.4.21 used by Centos 3.X) maps the kernel code of
vgettimeofday and vtime to address 0xFFFFFFFFFFFFFFF600000 and
0xFFFFFFFFFFFFFFF600400 respectively, and Glibc directly "call
*0xFFFFFFFFFFFFFFF600000" to invoke the gettimeofday system call, so to
avoid user/kernel context switches.

Then, are these two addresses free to use in Solaris. If so, how to retain
and map them; if not, I am afraid it may be impossible to support Centos 3.X
(Glibc-2.3.2) applications transparently on the X64 platform.

Wei Shen

[Attachment #5 (text/html)]

<div>Hi all,</div>
<div>&nbsp;</div>
<div>I meet some difficulty to add support for Linux vsyscall in lx64 brand.</div>
<div>&nbsp;</div>
<div>Linux kernel (2.4.21 used by Centos 3.X) maps the kernel code of vgettimeofday \
and vtime&nbsp;to address 0xFFFFFFFFFFFFFFF600000 and 0xFFFFFFFFFFFFFFF600400 \
respectively, and Glibc directly &quot;call *0xFFFFFFFFFFFFFFF600000&quot; to invoke \
the gettimeofday system call, so to avoid&nbsp;user/kernel context switches.</div>

<div>&nbsp;</div>
<div>Then, are these two addresses free to use in Solaris. If so, how to retain and \
map them; if not, I&nbsp;am afraid&nbsp;it may be impossible to support&nbsp;Centos \
3.X (Glibc-2.3.2)&nbsp;applications transparently on the X64 platform.</div>

<div>&nbsp;</div>
<div>Wei Shen</div>



_______________________________________________
brandz-discuss mailing list
brandz-discuss@opensolaris.org



[prev in list] [next in list] [prev in thread] [next in thread]