From: David Daney <ddaney@caviumnetworks.com>
To: "Kevin D. Kissell" <kevink@paralogos.com>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: Re: [PATCH 1/2] MIPS: Preliminary vdso.
Date: Wed, 22 Apr 2009 11:01:44 -0700 [thread overview]
Message-ID: <49EF5B88.90004@caviumnetworks.com> (raw)
In-Reply-To: <49EEE4EA.8040100@paralogos.com>
Kevin D. Kissell wrote:
> David Daney wrote:
>> This is a preliminary patch to add a vdso to all user processes.
>> Still missing are ELF headers and .eh_frame information. But it is
>> enough to allow us to move signal trampolines off of the stack.
>>
>> We allocate a single page (the vdso) and write all possible signal
>> trampolines into it. The stack is moved down by one page and the vdso
>> is mapped into this space.
>>
>> Signed-off-by: David Daney <ddaney@caviumnetworks.com>
> Note that for FPU-less CPUs, the kernel FP emulator also uses a user
> stack trampoline to execute instructions in the delay slots of emulated
> FP branches. I didn't see any of the math-emu modules being tweaked in
> either part of your patch. Presumably, one would want to move that
> operation into the vdso as well. With the proposed patch, I'm not sure
> whether things would continue working normally as before, still using
> the user stack, or whether the dsemulret code depends on something that
> is changed by the patch, and will now implode. Probably the former, but
> paranoia is not a character defect in OS kernel work. I don't have a
> test case handy (nor a test system any more), but compiling something
> like whetstone or linpack in C with a high degree of optimization will
> *probably* generate FP branches with live delay slots.
>
It is an ugly problem. I am trying to hack something up to fix it.
David Daney
next prev parent reply other threads:[~2009-04-23 6:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 21:30 [PATCH 0/2] MIPS: Move signal return trampolines off the stack David Daney
2009-04-21 21:33 ` [PATCH 1/2] MIPS: Preliminary vdso David Daney
2009-04-22 5:24 ` Shane McDonald
2009-04-22 15:18 ` David Daney
2009-04-22 9:35 ` Kevin D. Kissell
2009-04-22 18:01 ` David Daney [this message]
2009-04-24 7:20 ` Brian Foster
2009-04-24 7:50 ` Kevin D. Kissell
2009-04-24 15:30 ` David Daney
2009-04-27 7:19 ` Brian Foster
2009-04-27 12:51 ` Kevin D. Kissell
2009-04-27 15:54 ` David Daney
2009-04-27 17:27 ` Kevin D. Kissell
2009-04-27 18:26 ` David Daney
2009-04-22 17:50 ` David VomLehn
2009-04-22 18:05 ` David Daney
2009-04-22 18:28 ` David VomLehn
2009-04-21 21:33 ` [PATCH 2/2] MIPS: Move signal trampolines off of the stack David Daney
2009-04-22 17:57 ` David VomLehn
2009-04-22 18:04 ` [PATCH 0/2] MIPS: Move signal return trampolines off " David VomLehn
2009-04-22 18:13 ` David Daney
2009-04-22 18:31 ` David VomLehn
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=49EF5B88.90004@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=kevink@paralogos.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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