From: Andrew Haley <aph@redhat.com>
To: Richard Henderson <rth@redhat.com>, libffi-discuss@sourceware.org
Subject: Re: Constant trampoline pages
Date: Mon, 26 Jan 2015 10:02:00 -0000 [thread overview]
Message-ID: <54C61091.1060609@redhat.com> (raw)
In-Reply-To: <54C28ACB.8030702@redhat.com>
On 23/01/15 17:54, Richard Henderson wrote:
>
> Thoughts?
It looks a lot better than what we have now. I don't quite get how a
single page of allocated trampolines can suffice, though, even after
reading the code.
The big problem we've had with the dual-mapping trick was how to
survive a fork(). I wonder if your scheme could help with that.
Andrew.
next prev parent reply other threads:[~2015-01-26 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 17:54 Richard Henderson
2015-01-26 10:02 ` Andrew Haley [this message]
2015-01-26 17:31 ` Richard Henderson
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=54C61091.1060609@redhat.com \
--to=aph@redhat.com \
--cc=libffi-discuss@sourceware.org \
--cc=rth@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).