From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C33B3CDB465 for ; Mon, 16 Oct 2023 15:11:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233411AbjJPPLS (ORCPT ); Mon, 16 Oct 2023 11:11:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57954 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233109AbjJPPLR (ORCPT ); Mon, 16 Oct 2023 11:11:17 -0400 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F0058B4; Mon, 16 Oct 2023 08:11:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1697469075; x=1729005075; h=date:from:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=uxO8dRQXoxiQRzj4bSvfq5YWcf3cm6PAVAbnFH5KNhU=; b=Lz7DSCZ6Qq83VBiBTUoHt0u39JVrJALiGMraS+hrn2Xs4NXbTyhYjKrl W45kJOAf3/YUo4kgVYBQI+8FFMi3mHRFlCgmlUTB6B08DzMGPYfeag0CO KqNJBPcE+zI6Gx+xS+MjoEQ7s8i2ZmHyopFushKlygxICRRqNrkWVtaNj nxfgzzdei73AfAQOaZvvna8yZ/saIahjNjzzEo3CaVG//lwyitMoY9vMK erd7cHxV1vGD+AR5t/DpJYdiQIFD6kFjG+znLekaDoSVM1KZ/owlL0Tlb PRBXIySWrbQDs7M+oNu2QSxeNzSpcbJQBPnTSpqQBT6SPW0c/EynOlPw5 g==; X-IronPort-AV: E=McAfee;i="6600,9927,10863"; a="365809070" X-IronPort-AV: E=Sophos;i="6.03,229,1694761200"; d="scan'208";a="365809070" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Oct 2023 08:10:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10863"; a="785112698" X-IronPort-AV: E=Sophos;i="6.03,229,1694761200"; d="scan'208";a="785112698" Received: from rhaeussl-mobl.ger.corp.intel.com (HELO bhoerz-mobl1.ger.corp.intel.com) ([10.252.59.103]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Oct 2023 08:10:41 -0700 Date: Mon, 16 Oct 2023 18:10:39 +0300 (EEST) From: =?ISO-8859-15?Q?Ilpo_J=E4rvinen?= To: Bjorn Helgaas cc: linux-pci@vger.kernel.org, Jonathan Cameron , =?ISO-8859-2?Q?Krzysztof_Wilczy=F1ski?= , Lorenzo Pieralisi , LKML , Bjorn Helgaas Subject: Re: [PATCH 06/10] PCI/DPC: Use FIELD_GET() In-Reply-To: <3df6c8ea-888e-faa-5bae-e26b1f446ab3@linux.intel.com> Message-ID: <524d1789-6b57-aae-17b7-bf7ae49719dc@linux.intel.com> References: <20231013200249.GA1123559@bhelgaas> <3df6c8ea-888e-faa-5bae-e26b1f446ab3@linux.intel.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="8323329-245311799-1697469043=:1986" Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-245311799-1697469043=:1986 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT On Mon, 16 Oct 2023, Ilpo Järvinen wrote: > On Fri, 13 Oct 2023, Bjorn Helgaas wrote: > > > On Wed, Oct 11, 2023 at 02:01:13PM +0300, Ilpo Järvinen wrote: > > > On Tue, 10 Oct 2023, Bjorn Helgaas wrote: > > > > From: Bjorn Helgaas > > > > > > > > Use FIELD_GET() to remove dependences on the field position, i.e., the > > > > shift value. No functional change intended. > > > > > > > > Signed-off-by: Bjorn Helgaas > > > > --- > > > > drivers/pci/pcie/dpc.c | 9 +++++---- > > > > drivers/pci/quirks.c | 2 +- > > > > include/uapi/linux/pci_regs.h | 1 + > > > > 3 files changed, 7 insertions(+), 5 deletions(-) > > > > > > > > diff --git a/drivers/pci/pcie/dpc.c b/drivers/pci/pcie/dpc.c > > > > index 3ceed8e3de41..6e551f34ec63 100644 > > > > --- a/drivers/pci/pcie/dpc.c > > > > +++ b/drivers/pci/pcie/dpc.c > > > > @@ -8,6 +8,7 @@ > > > > > > > > #define dev_fmt(fmt) "DPC: " fmt > > > > > > > > +#include > > > > #include > > > > #include > > > > #include > > > > @@ -202,7 +203,7 @@ static void dpc_process_rp_pio_error(struct pci_dev *pdev) > > > > > > > > /* Get First Error Pointer */ > > > > pci_read_config_word(pdev, cap + PCI_EXP_DPC_STATUS, &dpc_status); > > > > - first_error = (dpc_status & 0x1f00) >> 8; > > > > + first_error = FIELD_GET(PCI_EXP_DPC_STATUS_FIRST_ERR, dpc_status); > > > > > > > > for (i = 0; i < ARRAY_SIZE(rp_pio_error_string); i++) { > > > > if ((status & ~mask) & (1 << i)) > > > > @@ -270,8 +271,8 @@ void dpc_process_error(struct pci_dev *pdev) > > > > pci_info(pdev, "containment event, status:%#06x source:%#06x\n", > > > > status, source); > > > > > > > > - reason = (status & PCI_EXP_DPC_STATUS_TRIGGER_RSN) >> 1; > > > > - ext_reason = (status & PCI_EXP_DPC_STATUS_TRIGGER_RSN_EXT) >> 5; > > > > + reason = FIELD_GET(PCI_EXP_DPC_STATUS_TRIGGER_RSN, status); > > > > + ext_reason = FIELD_GET(PCI_EXP_DPC_STATUS_TRIGGER_RSN_EXT, status); > > > > pci_warn(pdev, "%s detected\n", > > > > (reason == 0) ? "unmasked uncorrectable error" : > > > > (reason == 1) ? "ERR_NONFATAL" : > > > > > > BTW, it seems we're doing overlapping work here with many of these > > > patches. It takes some time to think these through one by one, I don't > > > just autorun through them with coccinelle so I've not posted my changes > > > yet. > > > > > > I went to a different direction here and named all the reasons too with > > > defines and used & to get the reason in order to be able to compare with > > > the named reasons. > > > > > > You also missed convering one 0xfff4 to use define (although I suspect it > > > never was your goal to go beyond FIELD_GET() here). > > > > Pure FIELD_GET() and FIELD_PREP() was my goal. > > > > If you have patches you prefer, I'll drop mine. I did these about a > > year ago and it seemed like the time to do something with them since > > you did the PCI_EXP_LNKSTA_NLW ones and to try to prevent overlapping > > work. Since we've started, I'd like to get as much of it done this > > cycle as possible. > > Okay, I suggest you keep your FIELD_GET/PREP() patch since mine is getting > more and more complicated. I can build a nice set of small changes about > what remains to do in DPC on top of your patch. Err, actually, there's still the naming of the define, should _FEP be used for First Error Pointer for consistency? You should make that small change into your patch if you think _FEP is better because of consistency. -- i. --8323329-245311799-1697469043=:1986--