Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [GIT PULL] x86/platform updates for v5.10
To:     Borislav Petkov <bp@suse.de>
Cc:     Linus Torvalds <torvalds@linux-foundation.org>,
        x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
References: <20201012101012.GD25311@zn.tnic>
 <CAHk-=wiwBYoAKQ6H=n0ppZfMe6nVDwDw6cruv7jxZZw4XEmUsg@mail.gmail.com>
 <c8cfb3d2-d3c4-6d8d-1dfd-aeb349e26303@hpe.com>
 <20201012212709.GM25311@zn.tnic>
From:   Mike Travis <mike.travis@hpe.com>
Message-ID: <f778b25e-68e7-98ec-9032-b35696948405@hpe.com>
Date:   Mon, 12 Oct 2020 14:42:27 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.8.1
MIME-Version: 1.0
In-Reply-To: <20201012212709.GM25311@zn.tnic>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk


On 10/12/2020 2:27 PM, Borislav Petkov wrote:
> On Mon, Oct 12, 2020 at 02:15:55PM -0700, Mike Travis wrote:
>>> Of course, it also looks like that 'uvh_nmi_mmrx_mask' thing is a
>>> write-only variable so it doesn't matter, but can we _please_ get this
>>> code fixed ASAP?
>>
>> Yes, I'll look at it right now.  Thanks.
> 
> As this variable is write-only you could simply zap it now with a patch
> ontop to fix the build and then introduce it properly later, when you
> really need it?
> 

It should have been an unsigned long instead of an int as Linus 
suggested.  I'm not sure it's a write only variable as I think the mask 
is used to check if the interrupt occurred (I'll have to look closer). 
I'm trying now to send the fixed patch.  It only has this change:

dog 74> diff -u patches/uv5_update_nmi{.v1,}
--- patches/uv5_update_nmi.v1   2020-10-12 16:30:06.083941459 -0500
+++ patches/uv5_update_nmi      2020-10-12 16:30:46.663903731 -0500
@@ -55,7 +55,7 @@
  +static unsigned long uvh_nmi_mmrx;            /* UVH_EVENT_OCCURRED0/1 */
  +static unsigned long uvh_nmi_mmrx_clear;      /* 
UVH_EVENT_OCCURRED0/1_ALIAS */
  +static int uvh_nmi_mmrx_shift;                        /* 
UVH_EVENT_OCCURRED0/1_EXTIO_INT0_SHFT */
-+static int uvh_nmi_mmrx_mask;                 /* 
UVH_EVENT_OCCURRED0/1_EXTIO_INT0_MASK */
++static unsigned long uvh_nmi_mmrx_mask;               /* 
UVH_EVENT_OCCURRED0/1_EXTIO_INT0_MASK */
  +static char *uvh_nmi_mmrx_type;                       /* "EXTIO_INT0" */
  +
  +/* Non-zero indicates newer SMM NMI handler present */

(or quoted)

> dog 74> diff -u patches/uv5_update_nmi{.v1,}
> --- patches/uv5_update_nmi.v1   2020-10-12 16:30:06.083941459 -0500
> +++ patches/uv5_update_nmi      2020-10-12 16:30:46.663903731 -0500
> @@ -55,7 +55,7 @@
>  +static unsigned long uvh_nmi_mmrx;            /* UVH_EVENT_OCCURRED0/1 */
>  +static unsigned long uvh_nmi_mmrx_clear;      /* UVH_EVENT_OCCURRED0/1_ALIAS */
>  +static int uvh_nmi_mmrx_shift;                        /* UVH_EVENT_OCCURRED0/1_EXTIO_INT0_SHFT */
> -+static int uvh_nmi_mmrx_mask;                 /* UVH_EVENT_OCCURRED0/1_EXTIO_INT0_MASK */
> ++static unsigned long uvh_nmi_mmrx_mask;               /* UVH_EVENT_OCCURRED0/1_EXTIO_INT0_MASK */
>  +static char *uvh_nmi_mmrx_type;                       /* "EXTIO_INT0" */
>  +
>  +/* Non-zero indicates newer SMM NMI handler present */