From: Moritz Fischer <mdf@kernel.org>
To: matthew.gerlach@linux.intel.com
Cc: Tom Rix <trix@redhat.com>,
hao.wu@intel.com, linux-fpga@vger.kernel.org,
linux-kernel@vger.kernel.org, yilun.xu@intel.com,
russell.h.weight@intel.com, mdf@kernel.org
Subject: Re: [PATCH] fpga: dfl: pci: gracefully handle misconfigured port entries
Date: Sun, 25 Apr 2021 18:21:57 -0700 [thread overview]
Message-ID: <YIYVtbgIpiH58y8H@epycbox.lan> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2104201217140.709797@rhweight-WRK1>
On Tue, Apr 20, 2021 at 12:19:42PM -0700, matthew.gerlach@linux.intel.com wrote:
>
>
> On Tue, 20 Apr 2021, Tom Rix wrote:
>
> >
> > On 4/20/21 10:27 AM, matthew.gerlach@linux.intel.com wrote:
> > > 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,
> > Does something similar need to be added to find_dfls_by_vsec ?
> > > 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;
> > > + }
> > > +
> > > 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);
Do you want pa or px here?
> >
> > why %pa,&len for instead of %u,len ?
> >
> > Tom
>
> Hi Tom,
>
> The variable len is of type resource_size_t, and I am following what it says
> to do in Documentation/core-api/printk-formats.rst:
>
> Physical address types phys_addr_t
> ----------------------------------
>
> ::
>
> %pa[p] 0x01234567 or 0x0123456789abcdef
>
> For printing a phys_addr_t type (and its derivatives, such as
> resource_size_t) which can vary based on build options, regardless of the
> width of the CPU data path.
>
> Passed by reference.
>
> Matthew
> >
> > > + continue;
> > > + }
> > > + len -= offset;
> > > + bars |= BIT(bar);
> > > dfl_fpga_enum_info_add_dfl(info, start, len);
> > > }
> > > } else if (dfl_feature_is_port(base)) {
> >
> >
- Moritz
next prev parent reply other threads:[~2021-04-26 1:22 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 [this message]
2021-04-21 5:25 ` Wu, Hao
2021-04-21 17:06 ` matthew.gerlach
2021-04-26 2:39 ` Wu, Hao
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=YIYVtbgIpiH58y8H@epycbox.lan \
--to=mdf@kernel.org \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.gerlach@linux.intel.com \
--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).