[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH v3 1/4] x86/xen.lds.S: Work around binutils build id alignment bug
On 08.09.2020 11:30, Trammell Hudson wrote: > On Tuesday, September 8, 2020 11:04 AM, Jan Beulich <jbeulich@xxxxxxxx> wrote: >> [...] >> Personally I think this kind of a workaround patch is something >> distros ought to be fine to carry, if they care about the >> functionality and only until they get around to upgrade their >> binutils. But I'll be happy to hear differing opinions. > > Y'all just merged something to support building with make 3.81, > released in *2006*, so why require a bleeding edge binutils to > work with the executable image? Building Xen has to work on the tool chain versions we document it works on (and we're in the process of discussing to raise the base line). Playing with the output of our build system is an entirely different thing. As with, I think, the majority of new features, distros would pick up your new functionality mainly for use in new versions, and hence would likely run with new binutils anyway by that time. >> I also don't see any mention anywhere of why it's 32 bytes, and not >> 16 or 64 or yet something else. > > It is 32 because you said 32 was probably fine. Well, that's then setting us up for running into the same issue again in case this "probably" turns out wrong. Referring to the size of the structure created by binutils to insert the build ID, otoh, could maybe give a proper reason. However, there's also the question whether this (not) functioning also depends on the particular size and/or alignment of the preceding section. Iirc this was the reason why you had thought there was a connection to live patching enabled / disabled in the build. Jan
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |