Received: by 2002:a05:7412:b995:b0:f9:9502:5bb8 with SMTP id it21csp2725936rdb; Tue, 26 Dec 2023 03:11:10 -0800 (PST) X-Google-Smtp-Source: AGHT+IHwLIDwaR8KWHOy3RW1QjZGcShmn+yLmOgp0gI9OnsnZZFVRTDMvKmi8+ZCtUKZ88BnjfhR X-Received: by 2002:a05:6358:528e:b0:174:c1a5:7724 with SMTP id g14-20020a056358528e00b00174c1a57724mr6144670rwa.42.1703589070497; Tue, 26 Dec 2023 03:11:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1703589070; cv=none; d=google.com; s=arc-20160816; b=UqV9v6w7eVAAmAdCmJkV/Qe/Z4o+R8RJFaKKZ+ttTenmhVyQ+CcBHSPCWUE4PALE4T f4r914F3ORmiO0eeshoK09OrYxC1rTijsewQ8WZvwJxGepTlEA8Hnc2YY/ToLsHVScQS 0Wx2v3nzDevh9BTlkWdprFE8HabDYxhZE47IM95CdZvr5SGnTJXAX3HP0zch11PQTyo7 0xBLTIA4WpAHYEIL/HpPFEGcKZ9woVGitf1w2ZsGSf/GCVJY4Iq8nMEsJcydshfTo7s1 sbiwskKTUIpxgMdL3eDNxcwNx82KZSZilpE0CbubZla07TdNtgeN9QMx2Shi6av/Dano 6Zkg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:date:message-id:dkim-signature; bh=+iJrkL3MoDalDrMKdAut7Js7jO3URQqsLVwvfwpjzFg=; fh=q9bjUO952xsaa1oVBNJWbOjLsx/jsnH3IJlC/xQKs3M=; b=ZWTfT/zUIlHjHRCBydRZegmEVBVNPW3PBXwil5AA1r18QSlfz4hFAGVbSTxlcdjK4F 9GByqcolOtZ1o5Wt/srLVFNsHieg7dj3KDXEZd8VhqTAEZiOkkEef+kCVpAxTE9dJq96 QkN+FzFfeor7vggT4NdzgU6jE0Tty1gX763Y/yHq5C0erDp0Nq/hruuOjMfIxu260SnO mPzkAMzkZ3h5Yy3DWm17t3vkra4BKcSSZrQH2PuHKIj8tvyxzHNZKAbfKKCEyVBN3Sxo GKSLU5wkRvMy/VHyQcLXLIrsQjOBi5xod9+zGEE5tgG2BLmhYqEd4MofJBofV/9CqvJZ LW0g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@quicinc.com header.s=qcppdkim1 header.b=GjoCsf76; spf=pass (google.com: domain of linux-kernel+bounces-11483-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-11483-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=quicinc.com Return-Path: Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [2604:1380:45e3:2400::1]) by mx.google.com with ESMTPS id lk10-20020a17090b33ca00b0028be7630b52si9722356pjb.75.2023.12.26.03.11.10 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 26 Dec 2023 03:11:10 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-11483-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1; Authentication-Results: mx.google.com; dkim=pass header.i=@quicinc.com header.s=qcppdkim1 header.b=GjoCsf76; spf=pass (google.com: domain of linux-kernel+bounces-11483-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-11483-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=quicinc.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id 18C45283052 for ; Tue, 26 Dec 2023 11:11:10 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 892D44E1DA; Tue, 26 Dec 2023 11:10:56 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=quicinc.com header.i=@quicinc.com header.b="GjoCsf76" X-Original-To: linux-kernel@vger.kernel.org Received: from mx0b-0031df01.pphosted.com (mx0b-0031df01.pphosted.com [205.220.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C0DAF4E1BB; Tue, 26 Dec 2023 11:10:53 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=quicinc.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=quicinc.com Received: from pps.filterd (m0279873.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.17.1.24/8.17.1.24) with ESMTP id 3BQ6lnBf011219; Tue, 26 Dec 2023 11:10:38 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; h= message-id:date:mime-version:subject:to:cc:references:from :in-reply-to:content-type:content-transfer-encoding; s= qcppdkim1; bh=+iJrkL3MoDalDrMKdAut7Js7jO3URQqsLVwvfwpjzFg=; b=Gj oCsf76VYgbr7c5yyVelOd2qm9txKwIjU6yUNmlEk+wKxZeC6Br68rSb8WBS7p7Ab j177FW4uZ1KHpQ40Ox36S2/7+PHr7ILJhHXnbeh25bUPnJ+IqDZFIsWFbOoob8oa zICpWb4o0j+YMqet5ezZ6KnAlyGs8trprmWJPrdiA1SvbFjHh4MBYtdc8q9AGQM+ BAyNgJ7a2jCbBkrUDjMltulgNUgMZlLk6kjbmSnM+jV4cFQjS7xHbbfJBqmINKPf /4pdJ3rB4DP1QXjmrPlyyqlwGR6AiB25Vq6OYmUiL4s9eXZ+X4h4QQM9xeerUX0d L1PfJ2smSZM0JiirV3Rw== Received: from nalasppmta03.qualcomm.com (Global_NAT1.qualcomm.com [129.46.96.20]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 3v78j5225d-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 26 Dec 2023 11:10:38 +0000 (GMT) Received: from nalasex01b.na.qualcomm.com (nalasex01b.na.qualcomm.com [10.47.209.197]) by NALASPPMTA03.qualcomm.com (8.17.1.5/8.17.1.5) with ESMTPS id 3BQBAak4029753 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 26 Dec 2023 11:10:36 GMT Received: from [10.216.36.143] (10.80.80.8) by nalasex01b.na.qualcomm.com (10.47.209.197) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.40; Tue, 26 Dec 2023 03:10:25 -0800 Message-ID: <2685432c-a086-4730-9dd6-8b8da1070697@quicinc.com> Date: Tue, 26 Dec 2023 16:40:21 +0530 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH net-next v8 3/3] net: stmmac: Add driver support for DWMAC5 common safety IRQ Content-Language: en-US To: Serge Semin CC: "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Vinod Koul , Bhupesh Sharma , Andy Gross , Bjorn Andersson , Konrad Dybcio , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Alexandre Torgue , Jose Abreu , Maxime Coquelin , , , , , , Prasad Sodagudi , Andrew Halaney , Rob Herring , References: <20231221073620.232619-1-quic_jsuraj@quicinc.com> <20231221073620.232619-4-quic_jsuraj@quicinc.com> From: Suraj Jaiswal In-Reply-To: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-ClientProxiedBy: nasanex01b.na.qualcomm.com (10.46.141.250) To nalasex01b.na.qualcomm.com (10.47.209.197) X-QCInternal: smtphost X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800 signatures=585085 X-Proofpoint-GUID: VnHk5vx7t0ifORKpDSgyryV4Os33YRQC X-Proofpoint-ORIG-GUID: VnHk5vx7t0ifORKpDSgyryV4Os33YRQC X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.997,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2023-12-09_02,2023-12-07_01,2023-05-22_02 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 mlxscore=0 mlxlogscore=999 priorityscore=1501 adultscore=0 bulkscore=0 phishscore=0 suspectscore=0 clxscore=1015 impostorscore=0 lowpriorityscore=0 malwarescore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2311290000 definitions=main-2312260083 Hi seren let me check below on test setup once & get back Thanks Suraj On 12/22/2023 8:05 PM, Serge Semin wrote: > On Fri, Dec 22, 2023 at 02:13:49PM +0530, Suraj Jaiswal wrote: >> HI Serge, >> please find commnet inline. >> >> Thanks >> Suraj >> >> On 12/21/2023 6:19 PM, Serge Semin wrote: >>> Hi Suraj >>> >>> On Thu, Dec 21, 2023 at 01:06:20PM +0530, Suraj Jaiswal wrote: >>>> Add support to listen HW safety IRQ like ECC(error >>>> correction code), DPP(data path parity), FSM(finite state >>>> machine) fault in common IRQ line. >>>> >>>> Signed-off-by: Suraj Jaiswal >>> >>> Thanks for taking my notes into account. One more comment is further >>> below. >>> >>>> --- >>>> drivers/net/ethernet/stmicro/stmmac/common.h | 1 + >>>> drivers/net/ethernet/stmicro/stmmac/stmmac.h | 3 ++ >>>> .../net/ethernet/stmicro/stmmac/stmmac_main.c | 37 +++++++++++++++++++ >>>> .../ethernet/stmicro/stmmac/stmmac_platform.c | 8 ++++ >>>> 4 files changed, 49 insertions(+) >>>> >>>> diff --git a/drivers/net/ethernet/stmicro/stmmac/common.h b/drivers/net/ethernet/stmicro/stmmac/common.h >>>> index 721c1f8e892f..b9233b09b80f 100644 >>>> --- a/drivers/net/ethernet/stmicro/stmmac/common.h >>>> +++ b/drivers/net/ethernet/stmicro/stmmac/common.h >>>> @@ -344,6 +344,7 @@ enum request_irq_err { >>>> REQ_IRQ_ERR_ALL, >>>> REQ_IRQ_ERR_TX, >>>> REQ_IRQ_ERR_RX, >>>> + REQ_IRQ_ERR_SFTY, >>>> REQ_IRQ_ERR_SFTY_UE, >>>> REQ_IRQ_ERR_SFTY_CE, >>>> REQ_IRQ_ERR_LPI, >>>> diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac.h b/drivers/net/ethernet/stmicro/stmmac/stmmac.h >>>> index 9f89acf31050..ca3d93851bed 100644 >>>> --- a/drivers/net/ethernet/stmicro/stmmac/stmmac.h >>>> +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac.h >>>> @@ -31,6 +31,7 @@ struct stmmac_resources { >>>> int wol_irq; >>>> int lpi_irq; >>>> int irq; >>>> + int sfty_irq; >>>> int sfty_ce_irq; >>>> int sfty_ue_irq; >>>> int rx_irq[MTL_MAX_RX_QUEUES]; >>>> @@ -297,6 +298,7 @@ struct stmmac_priv { >>>> void __iomem *ptpaddr; >>>> void __iomem *estaddr; >>>> unsigned long active_vlans[BITS_TO_LONGS(VLAN_N_VID)]; >>>> + int sfty_irq; >>>> int sfty_ce_irq; >>>> int sfty_ue_irq; >>>> int rx_irq[MTL_MAX_RX_QUEUES]; >>>> @@ -305,6 +307,7 @@ struct stmmac_priv { >>>> char int_name_mac[IFNAMSIZ + 9]; >>>> char int_name_wol[IFNAMSIZ + 9]; >>>> char int_name_lpi[IFNAMSIZ + 9]; >>>> + char int_name_sfty[IFNAMSIZ + 10]; >>>> char int_name_sfty_ce[IFNAMSIZ + 10]; >>>> char int_name_sfty_ue[IFNAMSIZ + 10]; >>>> char int_name_rx_irq[MTL_MAX_TX_QUEUES][IFNAMSIZ + 14]; >>>> diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c >>>> index 47de466e432c..7d4e827dfeab 100644 >>>> --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c >>>> +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c >>>> @@ -3592,6 +3592,10 @@ static void stmmac_free_irq(struct net_device *dev, >>>> if (priv->wol_irq > 0 && priv->wol_irq != dev->irq) >>>> free_irq(priv->wol_irq, dev); >>>> fallthrough; >>>> + case REQ_IRQ_ERR_SFTY: >>>> + if (priv->sfty_irq > 0 && priv->sfty_irq != dev->irq) >>>> + free_irq(priv->sfty_irq, dev); >>>> + fallthrough; >>>> case REQ_IRQ_ERR_WOL: >>>> free_irq(dev->irq, dev); >>>> fallthrough; >>>> @@ -3661,6 +3665,23 @@ static int stmmac_request_irq_multi_msi(struct net_device *dev) >>>> } >>>> } >>>> >>>> + /* Request the common Safety Feature Correctible/Uncorrectible >>>> + * Error line in case of another line is used >>>> + */ >>>> + if (priv->sfty_irq > 0 && priv->sfty_irq != dev->irq) { >>>> + int_name = priv->int_name_sfty; >>>> + sprintf(int_name, "%s:%s", dev->name, "safety"); >>>> + ret = request_irq(priv->sfty_irq, stmmac_safety_interrupt, >>>> + 0, int_name, dev); >>>> + if (unlikely(ret < 0)) { >>>> + netdev_err(priv->dev, >>>> + "%s: alloc sfty MSI %d (error: %d)\n", >>>> + __func__, priv->sfty_irq, ret); >>>> + irq_err = REQ_IRQ_ERR_SFTY; >>>> + goto irq_error; >>>> + } >>>> + } >>>> + >>>> /* Request the Safety Feature Correctible Error line in >>>> * case of another line is used >>>> */ >>>> @@ -3798,6 +3819,21 @@ static int stmmac_request_irq_single(struct net_device *dev) >>>> } >>>> } >>>> >>>> + /* Request the common Safety Feature Correctible/Uncorrectible >>>> + * Error line in case of another line is used >>>> + */ >>>> + if (priv->sfty_irq > 0 && priv->sfty_irq != dev->irq) { >>> >>>> + ret = request_irq(priv->sfty_irq, stmmac_safety_interrupt, >>>> + IRQF_SHARED, dev->name, dev); >>> >>> Just noticed yesterday that stmmac_safety_interrupt() is also called >>> from the stmmac_interrupt() handler which is supposed to be registered >>> on the generic "mac" IRQ. Won't it cause races around the CSRs >>> (doubtfully but still worth to note) and the errors handling >>> (stmmac_global_err()) in case if both IRQs are raised simultaneously? >>> At the very least it looks suspicious and worth double-checking. >>> >>> I also found out that nobody seemed to care that the same handler is >>> registered on MAC, WoL and LPI IRQ lines. Hmm, no race-related >>> problems have been reported so far for the platforms with separate >>> WoL/LPI IRQs. It's either a lucky coincident or the IRQs are always >>> assigned to the same CPU or the IRQs handle is indeed free of races. >>> In anyway it looks suspicious too. At the very least AFAICS the DMA >>> IRQ-handler is indeed racy on the status CSR access. It isn't >>> cleared-on-read, but write-one-to-clear. So the statistics might be >>> calculated more than once for the same CSR state. There might be some >>> other problems I failed to spot on the first glance. >>> >>> David, Eric, Jacub, Paolo, your opinion about the note above? >>> >>> -Serge(y) >>> > >> We are adding common IRQ similar to already present code for correcteable/uncorrecable https://elixir.bootlin.com/linux/latest/source/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c#L3592. > > From that perspective your change in stmmac_request_irq_multi_msi() is > correct, but stmmac_request_irq_single() is another story. The first > one method implies assigning the individual IRQ handlers to all > available lines. The later method assigns the _common_ handler to all > the lines. The common handler already calls the Safety IRQ handler - > stmmac_safety_feat_interrupt(). So should the safety IRQ line is > separately available it's possible to have the Safety IRQ handlers > executed concurrently - in framework of the common IRQ events handling > (if safety IRQ is raised during the common IRQ being handled) and > individual Safety IRQ. It's prune to the race condition I pointed out > to in my message above. Did you consider that problem? > >> Also, we need the sfty IRQ handling as soon as the fault occured & that can only be handled if we have handler attached with sfty IRQ. >> stmmac_interrupt() will only be triggerd when interrupt triggered for rx/tx packet . >> while registerting with sfty IRQ will get triggered as soon as emac HW detect the fault. > > Please read my comment more carefully. The safety IRQ can be raised > during the common IRQ handling, thus the > stmmac_safety_feat_interrupt() method might get to be concurrently > executed. > > -Serge(y) > >> >>>> + if (unlikely(ret < 0)) { >>>> + netdev_err(priv->dev, >>>> + "%s: ERROR: allocating the sfty IRQ %d (%d)\n", >>>> + __func__, priv->sfty_irq, ret); >>>> + irq_err = REQ_IRQ_ERR_SFTY; >>>> + goto irq_error; >>>> + } >>>> + } >>>> + >>>> return 0; >>>> >>>> irq_error: >>>> @@ -7462,6 +7498,7 @@ int stmmac_dvr_probe(struct device *device, >>>> priv->dev->irq = res->irq; >>>> priv->wol_irq = res->wol_irq; >>>> priv->lpi_irq = res->lpi_irq; >>>> + priv->sfty_irq = res->sfty_irq; >>>> priv->sfty_ce_irq = res->sfty_ce_irq; >>>> priv->sfty_ue_irq = res->sfty_ue_irq; >>>> for (i = 0; i < MTL_MAX_RX_QUEUES; i++) >>>> diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c >>>> index 70eadc83ca68..ab250161fd79 100644 >>>> --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c >>>> +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c >>>> @@ -743,6 +743,14 @@ int stmmac_get_platform_resources(struct platform_device *pdev, >>>> dev_info(&pdev->dev, "IRQ eth_lpi not found\n"); >>>> } >>>> >>>> + stmmac_res->sfty_irq = >>>> + platform_get_irq_byname_optional(pdev, "sfty"); >>>> + if (stmmac_res->sfty_irq < 0) { >>>> + if (stmmac_res->sfty_irq == -EPROBE_DEFER) >>>> + return -EPROBE_DEFER; >>>> + dev_info(&pdev->dev, "IRQ safety IRQ not found\n"); >>>> + } >>>> + >>>> stmmac_res->addr = devm_platform_ioremap_resource(pdev, 0); >>>> >>>> return PTR_ERR_OR_ZERO(stmmac_res->addr); >>>> -- >>>> 2.25.1 >>>> >>>>