This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Questions about VDSO

From: Steve Munroe <sjmunroe at us dot ibm dot com>
To: libc-hacker at sources dot redhat dot com
Cc: Paul Mackerras <pmac at au1 dot ibm dot com>
Date: Thu, 4 Nov 2004 16:11:39 -0600
Subject: Questions about VDSO

I am (finally) starting to look at enabling the GLIBC side of VDSO for 
PPC/PPC64 but have some questions about the details.

It looks like I need to define NEED_DL_SYSINFO in dl-sysdep.h  to set up 
the basic processing of AT_SYSINFO and AT_SYSINFO_EHDR. But looking at the 
i386 and ia64 examples it is not obvious what is needed for the general 
concept and what is specific to those platforms. For example I don't think 
PPC needs USE_DL_SYSINFO, DL_SYSINFO_DEFAULT, or DL_SYSINFO_IMPLEMENTATION 
because we are not changing the syscall mechanism for powerpc. Am I 
missing something?

Also there does not seem to be any kernel_feature specific enable for 
VDSO. So can I assume that a NEED_DL_SYSINFO GLIBC can run safely on a 
none VDSO kernel?

Steven J. Munroe
Linux on Power Toolchain Architect
IBM Corporation, Linux Technology Center

Follow-Ups:
- Re: Questions about VDSO
  - From: Roland McGrath

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]