From: Naveen Naidu <naveennaidu479@gmail.com> To: bhelgaas@google.com Cc: "Naveen Naidu" <naveennaidu479@gmail.com>, linux-kernel-mentees@lists.linuxfoundation.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, "Jonathan Derrick" <jonathan.derrick@linux.dev>, "Nirmal Patel" <nirmal.patel@linux.intel.com>, "Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>, "Rob Herring" <robh@kernel.org>, "Krzysztof Wilczyński" <kw@linux.com> Subject: [PATCH v2 17/24] PCI: vmd: Use RESPONSE_IS_PCI_ERROR() to check read from hardware Date: Fri, 15 Oct 2021 20:08:58 +0530 [thread overview] Message-ID: <0da4dfe7642bf89d954c7062a40566bf28d94da1.1634306198.git.naveennaidu479@gmail.com> (raw) In-Reply-To: <cover.1634306198.git.naveennaidu479@gmail.com> An MMIO read from a PCI device that doesn't exist or doesn't respond causes a PCI error. There's no real data to return to satisfy the CPU read, so most hardware fabricates ~0 data. Use RESPONSE_IS_PCI_ERROR() to check the response we get when we read data from hardware. This helps unify PCI error response checking and make error checks consistent and easier to find. Reviewed-by: Jonathan Derrick <jonathan.derrick@linux.dev> Signed-off-by: Naveen Naidu <naveennaidu479@gmail.com> --- drivers/pci/controller/vmd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/pci/controller/vmd.c b/drivers/pci/controller/vmd.c index a5987e52700e..db81bc4cfe8c 100644 --- a/drivers/pci/controller/vmd.c +++ b/drivers/pci/controller/vmd.c @@ -538,7 +538,7 @@ static int vmd_get_phys_offsets(struct vmd_dev *vmd, bool native_hint, int ret; ret = pci_read_config_dword(dev, PCI_REG_VMLOCK, &vmlock); - if (ret || vmlock == ~0) + if (ret || RESPONSE_IS_PCI_ERROR(&vmlock)) return -ENODEV; if (MB2_SHADOW_EN(vmlock)) { -- 2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Naveen Naidu <naveennaidu479@gmail.com> To: bhelgaas@google.com Cc: "Rob Herring" <robh@kernel.org>, "Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>, "Krzysztof Wilczyński" <kw@linux.com>, linux-kernel-mentees@lists.linuxfoundation.org, linux-kernel@vger.kernel.org, "Jonathan Derrick" <jonathan.derrick@linux.dev>, linux-pci@vger.kernel.org, "Nirmal Patel" <nirmal.patel@linux.intel.com> Subject: [PATCH v2 17/24] PCI: vmd: Use RESPONSE_IS_PCI_ERROR() to check read from hardware Date: Fri, 15 Oct 2021 20:08:58 +0530 [thread overview] Message-ID: <0da4dfe7642bf89d954c7062a40566bf28d94da1.1634306198.git.naveennaidu479@gmail.com> (raw) In-Reply-To: <cover.1634306198.git.naveennaidu479@gmail.com> An MMIO read from a PCI device that doesn't exist or doesn't respond causes a PCI error. There's no real data to return to satisfy the CPU read, so most hardware fabricates ~0 data. Use RESPONSE_IS_PCI_ERROR() to check the response we get when we read data from hardware. This helps unify PCI error response checking and make error checks consistent and easier to find. Reviewed-by: Jonathan Derrick <jonathan.derrick@linux.dev> Signed-off-by: Naveen Naidu <naveennaidu479@gmail.com> --- drivers/pci/controller/vmd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/pci/controller/vmd.c b/drivers/pci/controller/vmd.c index a5987e52700e..db81bc4cfe8c 100644 --- a/drivers/pci/controller/vmd.c +++ b/drivers/pci/controller/vmd.c @@ -538,7 +538,7 @@ static int vmd_get_phys_offsets(struct vmd_dev *vmd, bool native_hint, int ret; ret = pci_read_config_dword(dev, PCI_REG_VMLOCK, &vmlock); - if (ret || vmlock == ~0) + if (ret || RESPONSE_IS_PCI_ERROR(&vmlock)) return -ENODEV; if (MB2_SHADOW_EN(vmlock)) { -- 2.25.1 _______________________________________________ Linux-kernel-mentees mailing list Linux-kernel-mentees@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2021-10-15 14:46 UTC|newest] Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-15 14:35 [PATCH v2 00/24] Unify PCI error response checking Naveen Naidu 2021-10-15 14:35 ` Naveen Naidu 2021-10-15 14:35 ` Naveen Naidu 2021-10-15 14:35 ` Naveen Naidu 2021-10-15 14:35 ` Naveen Naidu 2021-10-15 14:35 ` Naveen Naidu 2021-10-15 14:28 ` [PATCH v2 01/24] PCI: Add PCI_ERROR_RESPONSE and it's related definitions Naveen Naidu 2021-10-15 14:28 ` Naveen Naidu 2021-10-20 13:24 ` Rob Herring 2021-10-20 13:24 ` Rob Herring 2021-10-15 14:28 ` [PATCH v2 02/24] PCI: Set error response in config access defines when ops->read() fails Naveen Naidu 2021-10-15 14:28 ` Naveen Naidu 2021-10-20 13:41 ` Rob Herring 2021-10-20 13:41 ` Rob Herring 2021-10-20 13:52 ` Pali Rohár 2021-10-20 13:52 ` Pali Rohár 2021-10-20 15:13 ` Naveen Naidu 2021-10-20 15:13 ` Naveen Naidu 2021-10-15 14:38 ` [PATCH v2 03/24] PCI: Unify PCI error response checking Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-20 13:13 ` Rob Herring 2021-10-20 13:13 ` Rob Herring 2021-10-20 15:15 ` Naveen Naidu 2021-10-20 15:15 ` Naveen Naidu 2021-10-15 14:38 ` [PATCH v2 04/24] PCI: Remove redundant error fabrication when device read fails Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-20 13:42 ` Rob Herring 2021-10-20 13:42 ` Rob Herring 2021-10-15 14:38 ` [PATCH v2 05/24] PCI: thunder: " Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 14:38 ` [PATCH v2 06/24] PCI: iproc: " Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 16:49 ` Ray Jui 2021-10-15 16:49 ` Ray Jui 2021-10-15 16:49 ` Ray Jui via Linux-kernel-mentees 2021-10-15 17:05 ` Naveen Naidu 2021-10-15 17:05 ` Naveen Naidu 2021-10-15 17:05 ` Naveen Naidu 2021-10-15 14:38 ` [PATCH v2 07/24] PCI: mediatek: " Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 14:38 ` [PATCH v2 08/24] PCI: exynos: " Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 14:38 ` [PATCH v2 09/24] PCI: histb: " Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 14:38 ` [PATCH v2 10/24] PCI: kirin: " Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 14:38 ` [PATCH v2 11/24] PCI: aardvark: " Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 14:38 ` [PATCH v2 12/24] PCI: mvebu: " Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 14:38 ` [PATCH v2 13/24] PCI: altera: " Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 14:38 ` [PATCH v2 14/24] PCI: rcar: " Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-18 11:32 ` Geert Uytterhoeven 2021-10-18 11:32 ` Geert Uytterhoeven 2021-10-18 11:51 ` Naveen Naidu 2021-10-18 11:51 ` Naveen Naidu 2021-10-18 12:00 ` Geert Uytterhoeven 2021-10-18 12:00 ` Geert Uytterhoeven 2021-10-15 14:38 ` [PATCH v2 15/24] PCI: rockchip: " Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 14:38 ` [PATCH v2 16/24] PCI/ERR: Use RESPONSE_IS_PCI_ERROR() to check read from hardware Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu [this message] 2021-10-15 14:38 ` [PATCH v2 17/24] PCI: vmd: " Naveen Naidu 2021-10-15 14:52 ` Naveen Naidu 2021-10-15 14:52 ` Naveen Naidu 2021-10-15 14:38 ` [PATCH v2 18/24] PCI: pciehp: " Naveen Naidu 2021-10-15 14:38 ` Naveen Naidu 2021-10-15 15:15 ` Naveen Naidu 2021-10-15 15:15 ` Naveen Naidu 2021-10-15 14:39 ` [PATCH v2 19/24] PCI/DPC: " Naveen Naidu 2021-10-15 14:39 ` Naveen Naidu 2021-10-15 14:39 ` Naveen Naidu 2021-10-15 14:39 ` [PATCH v2 20/24] PCI/PME: " Naveen Naidu 2021-10-15 14:39 ` Naveen Naidu 2021-10-15 14:39 ` [PATCH v2 21/24] PCI: cpqphp: " Naveen Naidu 2021-10-15 14:39 ` Naveen Naidu 2021-10-15 14:39 ` [PATCH v2 22/24] PCI: keystone: Use PCI_ERROR_RESPONSE to specify hardware error Naveen Naidu 2021-10-15 14:39 ` Naveen Naidu 2021-10-15 14:39 ` [PATCH v2 23/24] PCI: hv: Use PCI_ERROR_RESPONSE to specify hardware read error Naveen Naidu 2021-10-15 14:39 ` Naveen Naidu 2021-10-15 14:39 ` [PATCH v2 24/24] PCI: xgene: Use PCI_ERROR_RESPONSE to specify hardware error Naveen Naidu 2021-10-15 14:39 ` Naveen Naidu 2021-10-15 14:39 ` Naveen Naidu
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=0da4dfe7642bf89d954c7062a40566bf28d94da1.1634306198.git.naveennaidu479@gmail.com \ --to=naveennaidu479@gmail.com \ --cc=bhelgaas@google.com \ --cc=jonathan.derrick@linux.dev \ --cc=kw@linux.com \ --cc=linux-kernel-mentees@lists.linuxfoundation.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pci@vger.kernel.org \ --cc=lorenzo.pieralisi@arm.com \ --cc=nirmal.patel@linux.intel.com \ --cc=robh@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.