From: Florian Weimer <fw@deneb.enyo.de>
To: "H.J. Lu" <hjl.tools@gmail.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: <87o9witv25.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <CAMe9rOoRYXx6SEh0mmeP5vsT76a-OT2EHw-9ciRpEAy0ywtevA@mail.gmail.com> (H. J. Lu's message of "Mon, 20 Mar 2017 09:49:40 -0700")
* H. J. Lu:
> 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.
You can get an opaque handle from an address and feed it into dlinfo.
However, dlinfo only gives you access to the dynamic section, so
unless you put your section markup there as well, it won't help you.
I see that you are now considering dl_iterate_phdr, which gives you
access to the program headers, from where you can walk the section
headers. This looks like a good solution.
>> 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.
It's more for identifying roots to scan.
>> objects and their data sections. Can we make this work for multiple users?
>>
>
> What did you mean by "multiple users"?
Different libraries installing different hooks with similar
intentions.
next prev parent reply other threads:[~2017-03-30 19:37 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 ` 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 ` 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
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
2017-01-01 0:00 ` Florian Weimer [this message]
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
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=87o9witv25.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=carlos@redhat.com \
--cc=gnu-gabi@sourceware.org \
--cc=hegdesmailbox@gmail.com \
--cc=hjl.tools@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).