Re: [Xen-devel] [PATCH v4 4/9] version: Print build-id at bootup.

2016-09-09 Thread Ross Lagerwall
On 09/06/2016 05:57 PM, Konrad Rzeszutek Wilk wrote: On Wed, Aug 24, 2016 at 02:58:48AM -0600, Jan Beulich wrote: On 24.08.16 at 04:22, wrote: Livepatch expected at some point to be able to print the build-id during bootup, which it did not. The reason is that

Re: [Xen-devel] [PATCH v4 4/9] version: Print build-id at bootup.

2016-09-07 Thread Jan Beulich
>>> On 06.09.16 at 18:57, wrote: > On Wed, Aug 24, 2016 at 02:58:48AM -0600, Jan Beulich wrote: >> >>> On 24.08.16 at 04:22, wrote: >> > Livepatch expected at some point to be able to print the >> > build-id during bootup, which it did not. The

Re: [Xen-devel] [PATCH v4 4/9] version: Print build-id at bootup.

2016-09-06 Thread Konrad Rzeszutek Wilk
On Wed, Aug 24, 2016 at 02:58:48AM -0600, Jan Beulich wrote: > >>> On 24.08.16 at 04:22, wrote: > > Livepatch expected at some point to be able to print the > > build-id during bootup, which it did not. The reason is > > that xen_build_init and livepatch_init are both

Re: [Xen-devel] [PATCH v4 4/9] version: Print build-id at bootup.

2016-08-24 Thread Jan Beulich
>>> On 24.08.16 at 04:22, wrote: > Livepatch expected at some point to be able to print the > build-id during bootup, which it did not. The reason is > that xen_build_init and livepatch_init are both __initcall > type routines. This meant that when livepatch_init called >

[Xen-devel] [PATCH v4 4/9] version: Print build-id at bootup.

2016-08-23 Thread Konrad Rzeszutek Wilk
Livepatch expected at some point to be able to print the build-id during bootup, which it did not. The reason is that xen_build_init and livepatch_init are both __initcall type routines. This meant that when livepatch_init called xen_build_id, it would return -ENODATA as build_id_len was not