Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp3614863ybk; Tue, 19 May 2020 08:51:50 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyrpa+doxMuMnYcDEMa4hGAjpEQ2L1fzVNjKBxywrEMmbVPTFWy1JfZkp82I2DnViYRyrsm X-Received: by 2002:a05:6402:79a:: with SMTP id d26mr15668296edy.188.1589903510699; Tue, 19 May 2020 08:51:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1589903510; cv=none; d=google.com; s=arc-20160816; b=uQkbFCBspxLemppjskh4c+NNM1l+G6URWphwcaTG2ZwtpUlhHjPZe6NnITvpPtKS8p Y61UNR6SL97Oq7HuJdiwyQzYPa675NFVPJYyAbCeJQ09B1kNJXfT1rLQ08QuYUy3Ub5Y g2GpOnSGnZQA8Pg1Bb2GqR6pPRqyDQEEa7vBAcuWRP02Sjf5XkyACUN9/sbIBD2UCfFM J8JBShXmAkKWCJS2iCgGc2amQPzdhXXdmOHHDaC9kpk+BxdL/S3zj85toChIFLPqM4dS HOppuAr+YSdFHi0s+cnXKYUKeGrsSczNR+16v+QY8/8Qs/4tAPVkDBEX9HuMvus9qSid +Atg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:references:cc:to:subject:from; bh=SU70I9DzQaKIoU5wAiN7bM0OC/9kUegMxCBEFhWg1sk=; b=wYqine0UzgufB+oWMt0sfk/R7JHfr5qBbz7+8fWVfVE6Kev2eQpfSiJA2yocIYm6Wi vaHxCEmfqltFbZiTNyrwFQ+IZu6totJv37xmErQFzYq76v4FOybo6hf7ynhUEdMjSPT/ 3G38vSiR2Bc26ZK7lpwBvdoY6Hrmts50EeQNiUYWketKSoJ5H+ehW5kEmE/yBCBVdJzh KzcsVHW4FrvlawX8VyyT/y6rkhXbFrR8jKo0BjO2rtccFjjqJND04tUKEvrXmtkXMdJp VFkryoWoJerpLikgC1CZ5kiOVIWb3QaZ/51e/uhplmL98Abds56cppD0nC/tqWXLuE+D OFpQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id cb25si8274801edb.142.2020.05.19.08.51.27; Tue, 19 May 2020 08:51:50 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729161AbgESPrc (ORCPT + 99 others); Tue, 19 May 2020 11:47:32 -0400 Received: from foss.arm.com ([217.140.110.172]:35294 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729007AbgESPrc (ORCPT ); Tue, 19 May 2020 11:47:32 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 9BC0731B; Tue, 19 May 2020 08:47:31 -0700 (PDT) Received: from [192.168.0.14] (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 0CB2B3F305; Tue, 19 May 2020 08:47:30 -0700 (PDT) From: James Morse Subject: Re: [PATCH] firmware: arm_sdei: remove unused interfaces To: Xiongfeng Wang , Christoph Hellwig Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org References: <20200504164224.2842960-1-hch@lst.de> <7c127e49-b1c6-c7ac-69bf-9fc0a6dba4c4@arm.com> <6d0adc02-bcd8-2217-c145-d609528fbe77@huawei.com> Message-ID: <0ac1444b-bbdf-1efb-54e6-db90fe6ac707@arm.com> Date: Tue, 19 May 2020 16:47:21 +0100 User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <6d0adc02-bcd8-2217-c145-d609528fbe77@huawei.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Xiongfeng, On 05/05/2020 03:08, Xiongfeng Wang wrote: > On 2020/5/5 1:14, James Morse wrote: >> Hi Christoph, >> >> (CC: +Xiongfeng) >> >> Thanks for the reminder - I was just searching for who was using this. > > Thanks for CC me. We do have a driver that are using it. >> On 04/05/2020 17:42, Christoph Hellwig wrote: >>> The export symbols to register/unregister and enable/disable events >>> aren't ever used outside of arm_sdei.c, so mark them static. >> >> Xiongfeng, you have drivers using this, could they be posted upstream. Or can we stop >> exporting these? > > It's the SDEI Wathchdog which is used for hardlockup detection. But I wasn't > able to push it upstream because we have Pseudo-NMI in mainline. Hmm, that shouldn't be directly relevant, unless your SDEI watchdog is using the bindable-irq thing? If your firmware offers an event-id for the watchdog, please upstream the driver. Half of the event-id space is reserved for vendor stuff like this. If firmware needs to be told to re-configure the watchdog irq to make this work, then pNMI is a much better fit. Having firmware and linux modifying the irqchip hardware is a nightmare best avoided. >> (they were originally added for the GHES RAS thing, but by the time it was all merged >> upstream, it wasn't possible to build it as a module) > > The SDEI Watchdog driver also can't be built as a module. We still need to > modify the origin kernel. So I think this patch doesn't affect me. Thanks for CC me. Okay, I'll pick this up to drop the module exports. I'd prefer not to make all this static as these register/unregister calls are the interface that is supposed to be used. If we are going to gut it, we should do it completely. Thanks, James