>>> On 29.09.16 at 10:17, wrote:
> On Thu, Sep 29, 2016 at 02:01:46AM -0600, Jan Beulich wrote:
>> >>> On 29.09.16 at 09:51, wrote:
>> > On Thu, Sep 29, 2016 at 01:34:30AM -0600, Jan Beulich wrote:
>> >> >>> On 29.09.16 at 00:51,
On Thu, Sep 29, 2016 at 02:01:46AM -0600, Jan Beulich wrote:
> >>> On 29.09.16 at 09:51, wrote:
> > On Thu, Sep 29, 2016 at 01:34:30AM -0600, Jan Beulich wrote:
> >> >>> On 29.09.16 at 00:51, wrote:
> >> > --- a/xen/arch/x86/Makefile
> >> > +++
>>> On 29.09.16 at 09:51, wrote:
> On Thu, Sep 29, 2016 at 01:34:30AM -0600, Jan Beulich wrote:
>> >>> On 29.09.16 at 00:51, wrote:
>> > --- a/xen/arch/x86/Makefile
>> > +++ b/xen/arch/x86/Makefile
>> > @@ -91,7 +91,7 @@ endif
>> >
>> >
On Thu, Sep 29, 2016 at 01:34:30AM -0600, Jan Beulich wrote:
> >>> On 29.09.16 at 00:51, wrote:
> > Currently xen ELF end of image address is calculated using first line from
> > "nm -nr xen/xen-syms" output. However, potentially it may contain symbol
> > address not
>>> On 29.09.16 at 00:51, wrote:
> Currently xen ELF end of image address is calculated using first line from
> "nm -nr xen/xen-syms" output. However, potentially it may contain symbol
> address not related to the end of image in any way. It can happen if a symbol
> is
Currently xen ELF end of image address is calculated using first line from
"nm -nr xen/xen-syms" output. However, potentially it may contain symbol
address not related to the end of image in any way. It can happen if a symbol
is introduced with address larger than _end symbol address. Such