From: Andi Kleen <ak@muc.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sched_setaffinity usability
Date: Thu, 18 Mar 2004 22:23:18 +0100 [thread overview]
Message-ID: <m3r7vponnd.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <1BaUR-2V0-41@gated-at.bofh.it> (Ingo Molnar's message of "Thu, 18 Mar 2004 20:00:37 +0100")
Ingo Molnar <mingo@elte.hu> writes:
> * 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.
Yes, the x86-64 64bit vsyscalls predate all the vDSO work and haven't
been updated. It has a vDSO for 32bit programs though.
I guess it would be not that much work to add it for 64bit too.
I would not be opposed to it if somebody sends me patches.
This means my only objection is that an dwarf2 unwind table written
without the .cfi_* support in the assembler is incredibly ugly and
unmaintainable. I really don't want to have more such ugly tables. I
guess it would be best to force an binutils update for dwarf2
information.
-Andi
next parent reply other threads:[~2004-03-18 21:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` Andi Kleen [this message]
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
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
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=m3r7vponnd.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.