From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20112 invoked by alias); 20 Mar 2017 14:57:22 -0000 Mailing-List: contact gnu-gabi-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Post: List-Help: List-Subscribe: Sender: gnu-gabi-owner@sourceware.org Received: (qmail 20092 invoked by uid 89); 20 Mar 2017 14:57:21 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.99.2 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=no version=3.3.2 spammy=Hx-languages-length:750 X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on sourceware.org X-Spam-Level: X-HELO: mx1.redhat.com DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 65DC38051B Authentication-Results: ext-mx03.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx03.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=fweimer@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 65DC38051B Subject: Re: RFC: ABI support for special memory area To: "H.J. Lu" References: <88608944-14c9-9d28-80d1-32283521683b@gmail.com> <13b95ec6-45be-b02f-bb63-bc1835ecf396@redhat.com> Cc: Suprateeka R Hegde , Carlos O'Donell , gnu-gabi@sourceware.org From: Florian Weimer Message-ID: Date: Sun, 01 Jan 2017 00:00:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Mon, 20 Mar 2017 14:57:21 +0000 (UTC) X-SW-Source: 2017-q1/txt/msg00022.txt.bz2 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. I expect that libraries such as bdwgc might want to use the __gnu_mbind_setup callback as well, just to register freshly loaded shared objects and their data sections. Can we make this work for multiple users? Thanks, Florian