From: Ralf Baechle <ralf@linux-mips.org>
To: Manuel Lauss <manuel.lauss@googlemail.com>
Cc: David Daney <ddaney@caviumnetworks.com>, linux-mips@linux-mips.org
Subject: Re: [PATCH 2/3] MIPS: Preliminary vdso.
Date: Tue, 23 Feb 2010 22:35:18 +0100 [thread overview]
Message-ID: <20100223213518.GA19715@linux-mips.org> (raw)
In-Reply-To: <f861ec6f1002231240l40e1b07di6e751e40a2caa110@mail.gmail.com>
On Tue, Feb 23, 2010 at 09:40:38PM +0100, Manuel Lauss 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. Note
> > that emulation of branch delay slots in the FPU emulator still
> > requires 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.
>
> Is there anything special required (i.e. special glibc, ..) to make use of these
> fine patches?
No - the way the signal handlers return is almost entirely hidden from
userland. Only a few applications that have the need to unwind beyond
the signal stackframe may run into problems and have to be updated and
GDB is one of those that we identified.
Ralf
next prev parent reply other threads:[~2010-02-23 21:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 0:13 [PATCH 0/3] MIPS vdso and signal delivery optimization (v2) David Daney
2010-02-19 0:13 ` [PATCH 1/3] MIPS: Add SYSCALL to uasm David Daney
2010-03-16 19:55 ` Ralf Baechle
2010-02-19 0:13 ` [PATCH 2/3] MIPS: Preliminary vdso David Daney
2010-02-23 20:40 ` Manuel Lauss
2010-02-23 21:27 ` David Daney
2010-02-23 21:35 ` Ralf Baechle [this message]
2010-03-16 19:55 ` Ralf Baechle
2010-02-19 0:13 ` [PATCH 3/3] MIPS: Move signal trampolines off of the stack David Daney
2010-03-16 19:56 ` Ralf Baechle
2010-02-19 2:02 ` [PATCH 0/3] MIPS vdso and signal delivery optimization (v2) David Daney
2010-02-19 22:08 ` David Daney
2010-02-19 13:57 ` Ralf Baechle
2010-02-19 14:38 ` Ralf Baechle
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=20100223213518.GA19715@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@googlemail.com \
/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.