From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756212AbdKCMCv (ORCPT ); Fri, 3 Nov 2017 08:02:51 -0400 Received: from szxga04-in.huawei.com ([45.249.212.190]:9949 "EHLO szxga04-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753062AbdKCMCs (ORCPT ); Fri, 3 Nov 2017 08:02:48 -0400 Subject: Re: [PATCH] scsi: hisi_sas: select CONFIG_RAS To: Arnd Bergmann References: <20171102165059.213216-1-arnd@arndb.de> CC: "James E.J. Bottomley" , "Martin K. Petersen" , Xiang Chen , linux-scsi , Linux Kernel Mailing List , Linuxarm , Shiju Jose From: John Garry Message-ID: <50ad8f0e-9b21-4277-4be9-dfd6b82e5554@huawei.com> Date: Fri, 3 Nov 2017 12:02:16 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.202.227.238] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.59FC5ADA.0056,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0, ip=0.0.0.0, so=2014-11-16 11:51:01, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 1c167c3c6e0dce1fedc1d099d945a21e Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/11/2017 10:19, Arnd Bergmann wrote: > On Fri, Nov 3, 2017 at 11:14 AM, John Garry wrote: >> + Shiju, who authored the original patch >> > >>> index d42f29a5eb65..6ad8a6251d21 100644 >>> --- a/drivers/scsi/hisi_sas/Kconfig >>> +++ b/drivers/scsi/hisi_sas/Kconfig >>> @@ -4,6 +4,7 @@ config SCSI_HISI_SAS >>> depends on ARM64 || COMPILE_TEST >>> select SCSI_SAS_LIBSAS >>> select BLK_DEV_INTEGRITY >>> + select RAS >> >> >> My impression is that we don't want this. Correction: shouldn't want this. >> >> Do you have the .config for the broken build? I couldn't recreate this by >> turning off CONFIG_RAS. > > Uploaded to https://pastebin.com/A1rJYhDr > Maybe you were missing support for tracing in your configuration? > Thanks Arnd, I can see it now. However, as you said, it looks like this interface is not being used correctly, and I tend to agree. Actually this interface is intended for logging UEFI CPER non-standard records from kernel RAS/APEI framework to userspace. It is not intended for kernel peripheral driver logging (like this case). Until we get a community concensus on whether this is acceptable, I would rather revert the original patch. Thanks, John > Arnd > > . >