From: Ajay Agarwal <ajayagarwal@google.com>
To: William McVicker <willmcvicker@google.com>
Cc: "Jingoo Han" <jingoohan1@gmail.com>,
"Gustavo Pimentel" <gustavo.pimentel@synopsys.com>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Manu Gautam" <manugautam@google.com>,
"Sajid Dalvi" <sdalvi@google.com>,
"Serge Semin" <fancer.lancer@gmail.com>,
"Robin Murphy" <robin.murphy@arm.com>,
linux-pci@vger.kernel.org, kernel-team@android.com
Subject: Re: [PATCH v2] PCI: dwc: Strengthen the MSI address allocation logic
Date: Thu, 11 Jan 2024 23:32:18 +0530 [thread overview]
Message-ID: <ZaAtKqj45i3DNfiK@google.com> (raw)
In-Reply-To: <ZaAne_KeJaOYnBcu@google.com>
On Thu, Jan 11, 2024 at 09:38:03AM -0800, William McVicker wrote:
> Hi Ajay,
>
> Thanks for sending the patch!
>
> On 01/11/2024, Ajay Agarwal wrote:
> > There can be platforms that do not use/have 32-bit DMA addresses
> > but want to enumerate endpoints which support only 32-bit MSI
> > address. The current implementation of 32-bit IOVA allocation can
> > fail for such platforms, eventually leading to the probe failure.
> >
> > If there is a memory region reserved for the pci->dev, pick up
> > the MSI data from this region. This can be used by the platforms
> > described above.
> >
> > Else, if the memory region is not reserved, try to allocate a
> > 32-bit IOVA. Additionally, if this allocation also fails, attempt
> > a 64-bit allocation for probe to be successful. If the 64-bit MSI
> > address is allocated, then the EPs supporting 32-bit MSI address
> > will not work.
> >
> > Signed-off-by: Ajay Agarwal <ajayagarwal@google.com>
> > ---
> > Changelog since v1:
> > - Use reserved memory, if it exists, to setup the MSI data
> > - Fallback to 64-bit IOVA allocation if 32-bit allocation fails
> >
> > .../pci/controller/dwc/pcie-designware-host.c | 50 ++++++++++++++-----
> > drivers/pci/controller/dwc/pcie-designware.h | 1 +
> > 2 files changed, 39 insertions(+), 12 deletions(-)
> >
> > diff --git a/drivers/pci/controller/dwc/pcie-designware-host.c b/drivers/pci/controller/dwc/pcie-designware-host.c
> > index 7991f0e179b2..8c7c77b49ca8 100644
> > --- a/drivers/pci/controller/dwc/pcie-designware-host.c
> > +++ b/drivers/pci/controller/dwc/pcie-designware-host.c
> > @@ -331,6 +331,8 @@ static int dw_pcie_msi_host_init(struct dw_pcie_rp *pp)
> > u64 *msi_vaddr;
> > int ret;
> > u32 ctrl, num_ctrls;
> > + struct device_node *np;
> > + struct resource r;
> >
> > for (ctrl = 0; ctrl < MAX_MSI_CTRLS; ctrl++)
> > pp->irq_mask[ctrl] = ~0;
> > @@ -374,20 +376,44 @@ static int dw_pcie_msi_host_init(struct dw_pcie_rp *pp)
> > * order not to miss MSI TLPs from those devices the MSI target
> > * address has to be within the lowest 4GB.
> > *
> > - * Note until there is a better alternative found the reservation is
> > - * done by allocating from the artificially limited DMA-coherent
> > - * memory.
> > + * Check if there is memory region reserved for this device. If yes,
> > + * pick up the msi_data from this region. This will be helpful for
> > + * platforms that do not use/have 32-bit DMA addresses but want to use
> > + * endpoints which support only 32-bit MSI address.
> > + * Else, if the memory region is not reserved, try to allocate a 32-bit
> > + * IOVA. Additionally, if this allocation also fails, attempt a 64-bit
> > + * allocation. If the 64-bit MSI address is allocated, then the EPs
> > + * supporting 32-bit MSI address will not work.
> > */
> > - ret = dma_set_coherent_mask(dev, DMA_BIT_MASK(32));
> > - if (ret)
> > - dev_warn(dev, "Failed to set DMA mask to 32-bit. Devices with only 32-bit MSI support may not work properly\n");
> > + np = of_parse_phandle(dev->of_node, "memory-region", 0);
> > + if (np) {
> > + ret = of_address_to_resource(np, 0, &r);
> > + if (ret) {
> > + dev_err(dev, "No memory address assigned to the region\n");
> > + return ret;
> > + }
> >
> > - msi_vaddr = dmam_alloc_coherent(dev, sizeof(u64), &pp->msi_data,
> > - GFP_KERNEL);
> > - if (!msi_vaddr) {
> > - dev_err(dev, "Failed to alloc and map MSI data\n");
> > - dw_pcie_free_msi(pp);
> > - return -ENOMEM;
> > + pp->msi_data = r.start;
> > + } else {
> > + dev_dbg(dev, "No %s specified\n", "memory-region");
> > + ret = dma_set_coherent_mask(dev, DMA_BIT_MASK(32));
> > + if (ret)
> > + dev_warn(dev, "Failed to set DMA mask to 32-bit. Devices with only 32-bit MSI support may not work properly\n");
> > +
> > + msi_vaddr = dmam_alloc_coherent(dev, sizeof(u64), &pp->msi_data,
> > + GFP_KERNEL);
> > + if (!msi_vaddr) {
> > + dev_warn(dev, "Failed to alloc 32-bit MSI data. Attempting 64-bit now\n");
> > + dma_set_coherent_mask(dev, DMA_BIT_MASK(64));
> > + msi_vaddr = dmam_alloc_coherent(dev, sizeof(u64), &pp->msi_data,
> > + GFP_KERNEL);
> > + }
> > +
> > + if (!msi_vaddr) {
> > + dev_err(dev, "Failed to alloc and map MSI data\n");
> > + dw_pcie_free_msi(pp);
> > + return -ENOMEM;
> > + }
>
> Should we just put this second if-check inside the above fallback?
>
Yeah, we can do that. Will fix it in the next version after waiting for
comments from others.
> > }
> >
> > return 0;
> > diff --git a/drivers/pci/controller/dwc/pcie-designware.h b/drivers/pci/controller/dwc/pcie-designware.h
> > index 55ff76e3d384..c85cf4d56e98 100644
> > --- a/drivers/pci/controller/dwc/pcie-designware.h
> > +++ b/drivers/pci/controller/dwc/pcie-designware.h
> > @@ -317,6 +317,7 @@ struct dw_pcie_rp {
> > phys_addr_t io_bus_addr;
> > u32 io_size;
> > int irq;
> > + u8 coherent_dma_bits;
> > const struct dw_pcie_host_ops *ops;
> > int msi_irq[MAX_MSI_CTRLS];
> > struct irq_domain *irq_domain;
>
> Looks like this is a lingering change? Please drop.
>
Sorry about that. Will remove in the next version.
> Thanks,
> Will
>
> > --
> > 2.43.0.275.g3460e3d667-goog
> >
next prev parent reply other threads:[~2024-01-11 18:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 4:21 [PATCH v2] PCI: dwc: Strengthen the MSI address allocation logic Ajay Agarwal
2024-01-11 17:38 ` William McVicker
2024-01-11 18:02 ` Ajay Agarwal [this message]
2024-01-12 10:04 ` Serge Semin
2024-01-16 13:30 ` Robin Murphy
2024-01-16 20:47 ` Sajid Dalvi
[not found] ` <CAEbtx1=hoDTtpkavk7gp5tmcvdYj6euAuDsQYRPW=EDeVsbUqg@mail.gmail.com>
2024-01-16 21:02 ` Robin Murphy
2024-01-19 5:58 ` Ajay Agarwal
2024-01-30 17:22 ` Ajay Agarwal
2024-01-30 17:39 ` Robin Murphy
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=ZaAtKqj45i3DNfiK@google.com \
--to=ajayagarwal@google.com \
--cc=bhelgaas@google.com \
--cc=fancer.lancer@gmail.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=kernel-team@android.com \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=manugautam@google.com \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sdalvi@google.com \
--cc=willmcvicker@google.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