From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: torvalds@osdl.org, hch@infradead.org, drepper@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: sched_setaffinity usability
Date: Thu, 18 Mar 2004 19:55:48 +0100 [thread overview]
Message-ID: <20040318185548.GA4292@elte.hu> (raw)
In-Reply-To: <20040318183944.GA3710@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> x86-64 has a VDSO page as well, [...]
hm, i'm not sure this is the case. It does have a vsyscall page but
doesnt fill out AT_SYSINFO. ia64 seems to have something like a vdso,
passed down via AT_SYSINFO.
We could introduce AT_VDSO to standardize this, and switch x86 from
AT_SYSINFO to AT_VDSO, and all architectures that implement the VDSO.
I.e. something like the draft patch below. (this would also decrease the
size of the auxiliary table - glibc doesnt need to know the exception
header address.).
(this could also put an end to the AT_ bloat - eg. we could even get rid
of some of the constant AT_ values in the future: AT_PAGESZ, AT_CLKTCK,
AT_HWCAP, AT_PHENT and AT_FLAGS, and move them into the VDSO?)
Ingo
--- linux/include/linux/elf.h.orig
+++ linux/include/linux/elf.h
@@ -162,6 +162,7 @@ typedef __s64 Elf64_Sxword;
#define AT_PLATFORM 15 /* string identifying CPU for optimizations */
#define AT_HWCAP 16 /* arch dependent hints at CPU capabilities */
#define AT_CLKTCK 17 /* frequency at which times() increments */
+#define AT_VDSO 18 /* VDSO address */
#define AT_SECURE 23 /* secure mode boolean */
--- linux/include/asm-i386/elf.h.orig
+++ linux/include/asm-i386/elf.h
@@ -132,10 +132,9 @@ extern int dump_task_extended_fpu (struc
#define VSYSCALL_ENTRY ((unsigned long) &__kernel_vsyscall)
extern void __kernel_vsyscall;
-#define ARCH_DLINFO \
-do { \
- NEW_AUX_ENT(AT_SYSINFO, VSYSCALL_ENTRY); \
- NEW_AUX_ENT(AT_SYSINFO_EHDR, VSYSCALL_BASE); \
+#define ARCH_DLINFO \
+do { \
+ NEW_AUX_ENT(AT_VDSO, VSYSCALL_BASE); \
} while (0)
/*
next prev parent reply other threads:[~2004-03-18 18:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 8:05 sched_setaffinity usability Ulrich Drepper
2004-03-18 8:12 ` Tim Hockin
2004-03-18 8:22 ` Ulrich Drepper
2004-03-18 8:47 ` Ulrich Drepper
2004-03-18 9:45 ` Andrew Morton
2004-03-18 10:10 ` Andrew Morton
2004-03-18 11:29 ` Ingo Molnar
2004-03-18 12:07 ` Christoph Hellwig
2004-03-18 12:31 ` Ingo Molnar
2004-03-19 8:05 ` Ulrich Drepper
2004-03-18 15:55 ` Linus Torvalds
2004-03-18 18:24 ` Ingo Molnar
2004-03-18 18:33 ` Andrew Morton
2004-03-18 18:39 ` Ingo Molnar
2004-03-18 18:55 ` Ingo Molnar [this message]
2004-03-18 20:01 ` Andrea Arcangeli
2004-03-18 20:28 ` Ingo Molnar
2004-03-18 20:49 ` David Lang
2004-03-18 20:57 ` Randy.Dunlap
2004-03-18 21:06 ` Ingo Molnar
2004-03-18 21:07 ` Davide Libenzi
2004-03-18 21:46 ` Ingo Molnar
2004-03-19 1:37 ` Davide Libenzi
2004-03-19 9:02 ` Helge Hafting
2004-03-21 9:51 ` Ingo Molnar
2004-03-19 0:00 ` Paul Jackson
2004-03-18 17:47 ` sched_setaffinity usability -- other issue Chris Friesen
[not found] <1B0Ls-lY-27@gated-at.bofh.it>
[not found] ` <1B42z-3Lx-5@gated-at.bofh.it>
[not found] ` <1B4Fh-4sQ-3@gated-at.bofh.it>
[not found] ` <1B86P-8gq-69@gated-at.bofh.it>
[not found] ` <1Bars-2s6-29@gated-at.bofh.it>
[not found] ` <1BaKU-2Lg-49@gated-at.bofh.it>
[not found] ` <1BaKX-2Lg-61@gated-at.bofh.it>
[not found] ` <1BaUR-2V0-41@gated-at.bofh.it>
2004-03-18 21:23 ` sched_setaffinity usability Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040318185548.GA4292@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=drepper@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox