From: "H.J. Lu" <hjl.tools@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Suprateeka R Hegde <hegdesmailbox@gmail.com>,
"Carlos O'Donell" <carlos@redhat.com>,
gnu-gabi@sourceware.org
Subject: Re: RFC: ABI support for special memory area
Date: Sun, 01 Jan 2017 00:00:00 -0000 [thread overview]
Message-ID: <CAMe9rOoRYXx6SEh0mmeP5vsT76a-OT2EHw-9ciRpEAy0ywtevA@mail.gmail.com> (raw)
In-Reply-To: <db640770-65e7-6dc3-e9bc-85d86bc50387@redhat.com>
On Mon, Mar 20, 2017 at 7:57 AM, Florian Weimer <fweimer@redhat.com> wrote:
> On 03/16/2017 07:22 PM, H.J. Lu wrote:
>
>>> If the latter, why can't you use the existing ELF constructor mechanism
>>> for
>>> this? As far as I understand it, the call to __gnu_mbind_setup would
>>> just
>>> happen before the constructor calls.
>>
>>
>> That is correct. The issue is to access the ELF segment header for each
>> loaded object only once. There is no good way to get this info from
>> constructor.
>
>
> I think you can get the data in a pretty straightforward manner using
> dlinfo.
dlinfo is used to info from application. I don't see how it can be used
here.
> I expect that libraries such as bdwgc might want to use the
> __gnu_mbind_setup callback as well, just to register freshly loaded shared
Did you mean to mark pieces of memory garbage collectible? I guess it may
work.
> objects and their data sections. Can we make this work for multiple users?
>
What did you mean by "multiple users"? My proposal targets process memory
address space. It doesn't forbid sharing memory addresses among different
processes.
--
H.J.
next prev parent reply other threads:[~2017-03-20 16:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 0:00 H.J. Lu
2017-01-01 0:00 ` Carlos O'Donell
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Carlos O'Donell
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Florian Weimer
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Suprateeka R Hegde
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Suprateeka R Hegde
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Carlos O'Donell
2017-01-01 0:00 ` Suprateeka R Hegde
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Suprateeka R Hegde
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Florian Weimer
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Florian Weimer
2017-01-01 0:00 ` H.J. Lu [this message]
2017-01-01 0:00 ` Florian Weimer
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Suprateeka R Hegde
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Suprateeka R Hegde
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Suprateeka R Hegde
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Suprateeka R Hegde
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Suprateeka R Hegde
2017-01-01 0:00 ` H.J. Lu
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=CAMe9rOoRYXx6SEh0mmeP5vsT76a-OT2EHw-9ciRpEAy0ywtevA@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=gnu-gabi@sourceware.org \
--cc=hegdesmailbox@gmail.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).