From: Robin Murphy <robin.murphy@arm.com>
To: Bjorn Helgaas <helgaas@kernel.org>,
Ajay Agarwal <ajayagarwal@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>,
"William McVicker" <willmcvicker@google.com>,
"Serge Semin" <fancer.lancer@gmail.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v6] PCI: dwc: Strengthen the MSI address allocation logic
Date: Tue, 12 Mar 2024 13:52:05 +0000 [thread overview]
Message-ID: <46f1804c-429d-4d2a-8b68-91dbd0cebd00@arm.com> (raw)
In-Reply-To: <20240311165839.GA799766@bhelgaas>
On 11/03/2024 4:58 pm, Bjorn Helgaas wrote:
> On Wed, Feb 21, 2024 at 09:08:40PM +0530, Ajay Agarwal wrote:
>> There can be platforms that do not use/have 32-bit DMA addresses.
>> The current implementation of 32-bit IOVA allocation can fail for
>> such platforms, eventually leading to the probe failure.
>>
>> Try to allocate a 32-bit msi_data. If this allocation fails,
>> attempt a 64-bit address allocation. Please note that if the
>> 64-bit MSI address is allocated, then the EPs supporting 32-bit
>> MSI address only will not work.
>
> What happens when we fail to allocate a 32-bit address, we allocate a
> 64-bit address, we have an endpoint that only supports 32-bit
> addresses, and the driver tries to enable MSI? Does it fall back to
> INTx? Fail the MSI enable? Emit a warning?
In general __pci_write_msi_msg() will write the address, which will then
be truncated by the device, and when it subsequently tries to signal the
MSI it will go off into the weeds and not raise an interrupt. We'll have
already warned about failing to get a 32-bit MSI address when initially
probing the controller - although apparently now no longer explicitly
calling out the implication for 32-bit devices :( - which seems to be
about as much as we can reasonably do.
I suppose pci_write_msg_msi() could additionally scream if it sees
address_hi being nonzero when the given capability is only 32-bit, but
it still can't fail. Within the current design, I'm not sure we can
reasonably tell that a device is incompatible with the MSI domain until
irq_chip_compose_msi_msg(), by which point it's already way too late...
Thanks,
Robin.
>
>> Signed-off-by: Ajay Agarwal <ajayagarwal@google.com>
>> ---
>> Changelog since v5:
>> - Initialize temp variable 'msi_vaddr' to NULL
>> - Remove redundant print and check
>>
>> Changelog since v4:
>> - Remove the 'DW_PCIE_CAP_MSI_DATA_SET' flag
>> - Refactor the comments and msi_data allocation logic
>>
>> Changelog since v3:
>> - Add a new controller cap flag 'DW_PCIE_CAP_MSI_DATA_SET'
>> - Refactor the comments and print statements
>>
>> Changelog since v2:
>> - If the vendor driver has setup the msi_data, use the same
>>
>> 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 | 21 ++++++++++++-------
>> 1 file changed, 13 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/pci/controller/dwc/pcie-designware-host.c b/drivers/pci/controller/dwc/pcie-designware-host.c
>> index d5fc31f8345f..d15a5c2d5b48 100644
>> --- a/drivers/pci/controller/dwc/pcie-designware-host.c
>> +++ b/drivers/pci/controller/dwc/pcie-designware-host.c
>> @@ -328,7 +328,7 @@ static int dw_pcie_msi_host_init(struct dw_pcie_rp *pp)
>> struct dw_pcie *pci = to_dw_pcie_from_pp(pp);
>> struct device *dev = pci->dev;
>> struct platform_device *pdev = to_platform_device(dev);
>> - u64 *msi_vaddr;
>> + u64 *msi_vaddr = NULL;
>> int ret;
>> u32 ctrl, num_ctrls;
>>
>> @@ -379,15 +379,20 @@ static int dw_pcie_msi_host_init(struct dw_pcie_rp *pp)
>> * memory.
>> */
>> 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");
>> + if (!ret)
>> + msi_vaddr = dmam_alloc_coherent(dev, sizeof(u64), &pp->msi_data,
>> + GFP_KERNEL);
>>
>> - 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;
>> + dev_warn(dev, "Failed to allocate 32-bit MSI address\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 allocate MSI address\n");
>> + dw_pcie_free_msi(pp);
>> + return -ENOMEM;
>> + }
>> }
>>
>> return 0;
>> --
>> 2.44.0.rc0.258.g7320e95886-goog
>>
prev parent reply other threads:[~2024-03-12 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 15:38 [PATCH v6] PCI: dwc: Strengthen the MSI address allocation logic Ajay Agarwal
2024-02-21 17:32 ` Serge Semin
2024-02-21 23:13 ` William McVicker
2024-02-27 14:45 ` Manivannan Sadhasivam
2024-03-10 18:15 ` Krzysztof Wilczyński
2024-03-11 16:58 ` Bjorn Helgaas
2024-03-12 13:52 ` Robin Murphy [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=46f1804c-429d-4d2a-8b68-91dbd0cebd00@arm.com \
--to=robin.murphy@arm.com \
--cc=ajayagarwal@google.com \
--cc=bhelgaas@google.com \
--cc=fancer.lancer@gmail.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=helgaas@kernel.org \
--cc=jingoohan1@gmail.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=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;
as well as URLs for NNTP newsgroup(s).