From: "Wu, Hao" <hao.wu@intel.com>
To: "matthew.gerlach@linux.intel.com" <matthew.gerlach@linux.intel.com>
Cc: "trix@redhat.com" <trix@redhat.com>,
"linux-fpga@vger.kernel.org" <linux-fpga@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Xu, Yilun" <yilun.xu@intel.com>,
"Weight, Russell H" <russell.h.weight@intel.com>,
"mdf@kernel.org" <mdf@kernel.org>
Subject: RE: [PATCH] fpga: dfl: pci: gracefully handle misconfigured port entries
Date: Mon, 26 Apr 2021 02:39:34 +0000 [thread overview]
Message-ID: <DM6PR11MB3819A3CFA58B11427E813A2F85429@DM6PR11MB3819.namprd11.prod.outlook.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2104211001080.760078@rhweight-WRK1>
> On Wed, 21 Apr 2021, Wu, Hao wrote:
>
> >> Subject: [PATCH] fpga: dfl: pci: gracefully handle misconfigured port entries
> >>
> >> From: Matthew Gerlach <matthew.gerlach@linux.intel.com>
> >>
> >> Gracefully ignore misconfigured port entries encountered in
> >> incorrect FPGA images.
> >>
> >> Signed-off-by: Matthew Gerlach <matthew.gerlach@linux.intel.com>
> >> ---
> >> drivers/fpga/dfl-pci.c | 16 +++++++++++++++-
> >> 1 file changed, 15 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/fpga/dfl-pci.c b/drivers/fpga/dfl-pci.c
> >> index b44523e..660d3b6 100644
> >> --- a/drivers/fpga/dfl-pci.c
> >> +++ b/drivers/fpga/dfl-pci.c
> >> @@ -212,6 +212,7 @@ static int find_dfls_by_default(struct pci_dev *pcidev,
> >> int port_num, bar, i, ret = 0;
> >> resource_size_t start, len;
> >> void __iomem *base;
> >> + int bars = 0;
> >> u32 offset;
> >> u64 v;
> >>
> >> @@ -228,6 +229,7 @@ static int find_dfls_by_default(struct pci_dev *pcidev,
> >> if (dfl_feature_is_fme(base)) {
> >> start = pci_resource_start(pcidev, 0);
> >> len = pci_resource_len(pcidev, 0);
> >> + bars |= BIT(0);
> >>
> >> dfl_fpga_enum_info_add_dfl(info, start, len);
> >>
> >> @@ -253,9 +255,21 @@ static int find_dfls_by_default(struct pci_dev
> *pcidev,
> >> */
> >> bar = FIELD_GET(FME_PORT_OFST_BAR_ID, v);
> >> offset = FIELD_GET(FME_PORT_OFST_DFH_OFST, v);
> >> + if (bars & BIT(bar)) {
> >> + dev_warn(&pcidev->dev, "skipping bad port
> >> BAR %d\n", bar);
> >> + continue;
> >> + }
> >
> > Will it be a real problem that multiple ports are inside one BAR but different
> offsets?
> >
> > Hao
>
> I don't think multiple ports within a single BAR is something that has
> been supported in the past. The genesis for this patch was a
> misconfigured port entry pointing to BAR0. BAR0 had already been mapped
> for the FME and remapping BAR0 failed resulting in enumeration failure.
could some products put the port in BAR0? Or multiple ports in one BAR.
As we consider this is a common driver can be reused and maintained for
a long time, so I hope that we don't put limitation setup only for some
specific products.
Hao
>
> Matthew
>
> >
> >> +
> >> start = pci_resource_start(pcidev, bar) + offset;
> >> - len = pci_resource_len(pcidev, bar) - offset;
> >> + len = pci_resource_len(pcidev, bar);
> >> + if (offset >= len) {
> >> + dev_warn(&pcidev->dev, "bad port
> >> offset %u >= %pa\n",
> >> + offset, &len);
> >> + continue;
> >> + }
> >>
> >> + len -= offset;
> >> + bars |= BIT(bar);
> >> dfl_fpga_enum_info_add_dfl(info, start, len);
> >> }
> >> } else if (dfl_feature_is_port(base)) {
> >> --
> >> 1.8.3.1
> >
> >
prev parent reply other threads:[~2021-04-26 2:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 17:27 [PATCH] fpga: dfl: pci: gracefully handle misconfigured port entries matthew.gerlach
2021-04-20 18:49 ` Tom Rix
2021-04-20 19:19 ` matthew.gerlach
2021-04-26 1:21 ` Moritz Fischer
2021-04-21 5:25 ` Wu, Hao
2021-04-21 17:06 ` matthew.gerlach
2021-04-26 2:39 ` Wu, Hao [this message]
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=DM6PR11MB3819A3CFA58B11427E813A2F85429@DM6PR11MB3819.namprd11.prod.outlook.com \
--to=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.gerlach@linux.intel.com \
--cc=mdf@kernel.org \
--cc=russell.h.weight@intel.com \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).