Re: [Xen-devel] [PATCH v3 2/3] XENVER_build_id: Provide ld-embedded build-ids (v8)

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 14.01.16 at 10:07, <mpohlack@xxxxxxxxxx> wrote:
> On 14.01.2016 09:58, Jan Beulich wrote:
>>>>> On 14.01.16 at 03:02, <konrad@xxxxxxxxxx> 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?

"Stripped" isn't the right term, because the uncompressed variant
of xen.gz is farther away from xen-syms than just being stripped.
But yes, all this is about is that it should be possible to obtain
xen.gz's and xen.efi's build IDs as well.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel