From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Pohlack Subject: Re: [PATCH v3 2/3] XENVER_build_id: Provide ld-embedded build-ids (v8) Date: Thu, 14 Jan 2016 10:07:05 +0100 Message-ID: <56976539.5060505@amazon.com> References: <1452219920-14043-1-git-send-email-konrad.wilk@oracle.com> <1452219920-14043-3-git-send-email-konrad.wilk@oracle.com> <5695370702000078000C6047@prv-mh.provo.novell.com> <20160112164301.GC17685@char.us.oracle.com> <56953F2D02000078000C60DB@prv-mh.provo.novell.com> <20160114020226.GA8254@x230.dumpdata.com> <5697715702000078000C693B@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aJdsm-0005NG-9y for xen-devel@lists.xenproject.org; Thu, 14 Jan 2016 09:07:52 +0000 In-Reply-To: <5697715702000078000C693B@prv-mh.provo.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich , Konrad Rzeszutek Wilk Cc: wei.liu2@citrix.com, ian.campbell@citrix.com, andrew.cooper3@citrix.com, ian.jackson@eu.citrix.com, mpohlack@amazon.de, xen-devel@lists.xenproject.org, dgdegra@tycho.nsa.gov List-Id: xen-devel@lists.xenproject.org On 14.01.2016 09:58, Jan Beulich wrote: >>>> On 14.01.16 at 03:02, wrote: >>>> Or are you suggesting that perhaps the kernel should at boot time >>>> print the build-id (like it does the changset)? >>> >>> Perhaps, albeit to me that's a bit orthogonal to being able to find out >>> the build ID for a given binary. >> >> I can make some magic objdump + awk to extract the buildid from >> the hypervisor and deposit as a text file in /usr/../xen/debug? >> Similar to how xen-syms is copied there? >> >> Would that work? > > No, because of ... > >> But I am a bit lost of what your use-case is? > > ... this is about holding a standalone Xen binary in hands, and > wanting to identify its build ID. Not sure how limited the range of > permitted things is in the simplified ELF binary we generate - > perhaps adding a proper PT_NOTE segment there would do? To clarify your question: readelf -n xen-syms should result in finding and dumping the build ID. The original patch to xen.lds did achieve that. Is that enough for you or do you want that to work as well for the stripped xen file? Martin Amazon Development Center Germany GmbH Berlin - Dresden - Aachen main office: Krausenstr. 38, 10117 Berlin Geschaeftsfuehrer: Dr. Ralf Herbrich, Christian Schlaeger Ust-ID: DE289237879 Eingetragen am Amtsgericht Charlottenburg HRB 149173 B