From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.kernel.org ([198.145.29.99]:41412 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752298AbeEKFZg (ORCPT ); Fri, 11 May 2018 01:25:36 -0400 Date: Fri, 11 May 2018 07:24:40 +0200 From: Greg KH To: mike.travis@hpe.com Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Andrew Morton , Dimitri Sivanich , Russ Anderson , Andrew Banman , jgross@suse.com, dan.j.williams@intel.com, mhocko@suse.com, kirill.shutemov@linux.intel.com, x86@kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH 2/3] x86/platform/UV: Use new set memory block size function Message-ID: <20180511052440.GD2902@kroah.com> References: <20180510231832.035433756@stormcage.americas.sgi.com> <20180510231832.321834876@stormcage.americas.sgi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180510231832.321834876@stormcage.americas.sgi.com> Sender: stable-owner@vger.kernel.org List-ID: On Thu, May 10, 2018 at 06:18:34PM -0500, mike.travis@hpe.com wrote: > Add a call to the new function to "adjust" the current fixed UV memory > block size of 2GB so it can be changed to a different physical boundary. > This accommodates changes in the Intel BIOS, and therefore UV BIOS, which > now can align boundaries different than the previous UV standard of 2GB. > It also flags any UV Mem boundaries that cause a change in the mem block > size boundary. > > Signed-off-by: Mike Travis > Reviewed-by: Andrew Banman > --- > arch/x86/kernel/apic/x2apic_uv_x.c | 49 ++++++++++++++++++++++++++++++++++--- > 1 file changed, 46 insertions(+), 3 deletions(-) > This is not the correct way to submit patches for inclusion in the stable kernel tree. Please read: https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html for how to do this properly.