From: "H. Peter Anvin" Subject: Re: [RFC 20/22] x86/relocs: Add option to generate 64-bit relocations Date: Wed, 19 Jul 2017 15:33:13 -0700 Message-ID: References: <20170718223333.110371-1-thgarnie@google.com> <20170718223333.110371-21-thgarnie@google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: x86@kernel.org, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org, kvm@vger.kernel.org, linux-pm@vger.kernel.org, linux-arch@vger.kernel.org, linux-sparse@vger.kernel.org, kernel-hardening@lists.openwall.com To: Thomas Garnier , Herbert Xu , "David S . Miller" , Thomas Gleixner , Ingo Molnar , Peter Zijlstra , Josh Poimboeuf , Arnd Bergmann , Matthias Kaehlcke , Boris Ostrovsky , Juergen Gross , Paolo Bonzini , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , Joerg Roedel , Andy Lutomirski , Borislav Petkov , "Kirill A . Shutemov" , Brian Gerst , Borislav Petkov , Christian Borntraeger , Return-path: List-Post: List-Help: List-Unsubscribe: List-Subscribe: In-Reply-To: <20170718223333.110371-21-thgarnie@google.com> Content-Language: en-US List-Id: linux-crypto.vger.kernel.org On 07/18/17 15:33, Thomas Garnier wrote: > The x86 relocation tool generates a list of 32-bit signed integers. There > was no need to use 64-bit integers because all addresses where above the 2G > top of the memory. > > This change add a large-reloc option to generate 64-bit unsigned integers. > It can be used when the kernel plan to go below the top 2G and 32-bit > integers are not enough. Why on Earth? This would only be necessary if the *kernel itself* was more than 2G, which isn't going to happen for the forseeable future. -hpa