From: Martin Pohlack <mpohlack@amazon.com>
To: Jan Beulich <JBeulich@suse.com>,
Konrad Rzeszutek Wilk <konrad@kernel.org>
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
Subject: Re: [PATCH v3 2/3] XENVER_build_id: Provide ld-embedded build-ids (v8)
Date: Thu, 14 Jan 2016 10:07:05 +0100 [thread overview]
Message-ID: <56976539.5060505@amazon.com> (raw)
In-Reply-To: <5697715702000078000C693B@prv-mh.provo.novell.com>
On 14.01.2016 09:58, Jan Beulich wrote:
>>>> On 14.01.16 at 03:02, <konrad@kernel.org> 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
next prev parent reply other threads:[~2016-01-14 9:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 2:25 [PATCH v3] Add build-id to XENVER hypercall Konrad Rzeszutek Wilk
2016-01-08 2:25 ` [PATCH v3 1/3] xsm/xen_version: Add XSM for the xen_version hypercall (v6) Konrad Rzeszutek Wilk
2016-01-08 17:57 ` Daniel De Graaf
2016-01-12 16:08 ` Jan Beulich
2016-01-08 2:25 ` [PATCH v3 2/3] XENVER_build_id: Provide ld-embedded build-ids (v8) Konrad Rzeszutek Wilk
2016-01-12 16:25 ` Jan Beulich
2016-01-12 16:43 ` Konrad Rzeszutek Wilk
2016-01-12 17:00 ` Jan Beulich
2016-01-14 2:02 ` Konrad Rzeszutek Wilk
2016-01-14 8:58 ` Jan Beulich
2016-01-14 9:07 ` Martin Pohlack [this message]
2016-01-14 9:14 ` Jan Beulich
2016-01-25 15:16 ` Konrad Rzeszutek Wilk
2016-01-25 16:10 ` Jan Beulich
2016-01-15 21:49 ` Konrad Rzeszutek Wilk
2016-01-18 8:51 ` Jan Beulich
2016-01-19 16:05 ` Konrad Rzeszutek Wilk
2016-01-19 16:36 ` Jan Beulich
2016-01-19 16:47 ` Konrad Rzeszutek Wilk
2016-02-17 11:37 ` Ian Jackson
2016-01-08 2:25 ` [PATCH v3 3/3] libxl: info: Display build_id of the hypervisor Konrad Rzeszutek Wilk
2016-01-11 14:12 ` Wei Liu
2016-01-14 2:58 ` Konrad Rzeszutek Wilk
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=56976539.5060505@amazon.com \
--to=mpohlack@amazon.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=konrad@kernel.org \
--cc=mpohlack@amazon.de \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.