public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: "Bjorn Helgaas" <helgaas@kernel.org>,
	"Jingoo Han" <jingoohan1@gmail.com>,
	"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Rob Herring" <robh@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH 2/2] PCI: dwc: ep: Use align addr function for dw_pcie_ep_raise_{msi,msix}_irq()
Date: Fri, 1 Nov 2024 19:25:18 +0100	[thread overview]
Message-ID: <ZyUdDqLwirSZEmvw@x1-carbon> (raw)
In-Reply-To: <7c30ed21-5d48-414a-a943-68ff74b4f23e@kernel.org>

On Fri, Nov 01, 2024 at 07:36:51AM +0900, Damien Le Moal wrote:
> On 11/1/24 05:28, Bjorn Helgaas wrote:
> > On Thu, Oct 17, 2024 at 03:20:55PM +0200, Niklas Cassel wrote:
> >> Use the dw_pcie_ep_align_addr() function to calculate the alignment in
> >> dw_pcie_ep_raise_{msi,msix}_irq() instead of open coding the same.
> >>
> >> Signed-off-by: Niklas Cassel <cassel@kernel.org>
> >> ---
> >>  .../pci/controller/dwc/pcie-designware-ep.c    | 18 +++++++++---------
> >>  1 file changed, 9 insertions(+), 9 deletions(-)
> >>
> >> diff --git a/drivers/pci/controller/dwc/pcie-designware-ep.c b/drivers/pci/controller/dwc/pcie-designware-ep.c
> >> index 20f67fd85e83..9bafa62bed1d 100644
> >> --- a/drivers/pci/controller/dwc/pcie-designware-ep.c
> >> +++ b/drivers/pci/controller/dwc/pcie-designware-ep.c
> >> @@ -503,7 +503,8 @@ int dw_pcie_ep_raise_msi_irq(struct dw_pcie_ep *ep, u8 func_no,
> >>  	u32 msg_addr_lower, msg_addr_upper, reg;
> >>  	struct dw_pcie_ep_func *ep_func;
> >>  	struct pci_epc *epc = ep->epc;
> >> -	unsigned int aligned_offset;
> >> +	size_t msi_mem_size = epc->mem->window.page_size;
> >> +	size_t offset;
> >>  	u16 msg_ctrl, msg_data;
> >>  	bool has_upper;
> >>  	u64 msg_addr;
> >> @@ -531,14 +532,13 @@ int dw_pcie_ep_raise_msi_irq(struct dw_pcie_ep *ep, u8 func_no,
> >>  	}
> >>  	msg_addr = ((u64)msg_addr_upper) << 32 | msg_addr_lower;
> >>  
> >> -	aligned_offset = msg_addr & (epc->mem->window.page_size - 1);
> >> -	msg_addr = ALIGN_DOWN(msg_addr, epc->mem->window.page_size);
> >> +	msg_addr = dw_pcie_ep_align_addr(epc, msg_addr, &msi_mem_size, &offset);
> >>  	ret = dw_pcie_ep_map_addr(epc, func_no, 0, ep->msi_mem_phys, msg_addr,
> >> -				  epc->mem->window.page_size);
> >> +				  msi_mem_size);
> > 
> > I haven't worked through this; just double checking that this is
> > correct.  Previously we did ALIGN_DOWN() here, but
> > dw_pcie_ep_align_addr() uses ALIGN() (not ALIGN_DOWN()).  Similar
> > below in dw_pcie_ep_raise_msix_irq().
> 
> The ALIGN() in dw_pcie_ep_align_addr() is for the mapping size. The address is
> aligned down manually:
> 
> 	return pci_addr & ~mask;
> 
> So it is the same. We could change dw_pcie_ep_align_addr() to do:
> 
> 	return ALIGN_DOWN(pci_addr, epc->mem->window.page_size);
> 
> But given that the offset calculation needs the alignment mask anyway, using
> the mask variable directly seems natural.

I agree.


> 
> So this is functionnally identical for the PCI address being mapped, and it is
> even better for the mapping size since this was passing
> epc->mem->window.page_size before but if the PCI address range crosses over a
> page_size boundary, we actually need 2 x page_size as the mapping size...
> 
> Which makes me realized that there is something still wrong: the memory being
> mapped (ep->msi_mem) is at most one page:
> 
> 	ep->msi_mem = pci_epc_mem_alloc_addr(epc, &ep->msi_mem_phys,
> 					     epc->mem->window.page_size);
> 	if (!ep->msi_mem) {
> 		ret = -ENOMEM;
> 		dev_err(dev, "Failed to reserve memory for MSI/MSI-X\n");
> 		goto err_exit_epc_mem;
> 	}
> 
> But we may need up to 2 pages depending on the PCI address we get for the
> MSI/MSIX. So we need to fix that as well I think.
> 
> Niklas, thoughts ?

Hmm.. the MSI data that we want to map is just two bytes.
It is just that the minimum mapping we can do is epc->mem->window.page_size.

On e.g. rk3588 the page_size is 64k.

I guess that we might be unlucky and get the MSI data at an offset that is
at the end of the page.

But considering that we just need 2 bytes (for MSI, 4 bytes for MSI-X),
and that the PCI word size is 4 bytes, I don't see a problem with the
current code.


While the allocation of the msi_mem should still be page_size:
ep->msi_mem = pci_epc_mem_alloc_addr(epc, &ep->msi_mem_phys,
                                     epc->mem->window.page_size);

I guess that we could change dw_pcie_ep_raise_msi_irq() from:
size_t msi_mem_size = epc->mem->window.page_size;
to:
size_t msi_mem_size = 2;

and change dw_pcie_ep_raise_msix_irq() from:
size_t msi_mem_size = epc->mem->window.page_size;
to:
size_t msi_mem_size = 4;

To make the code strictly more correct for a reader, but I
don't think that there is a problem with the current code.


Kind regards,
Niklas

  reply	other threads:[~2024-11-01 18:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17 13:20 [PATCH 0/2] PCI: dwc: ep: Minor alignment cleanups Niklas Cassel
2024-10-17 13:20 ` [PATCH 1/2] PCI: dwc: ep: Fix dw_pcie_ep_align_addr() Niklas Cassel
2024-10-17 15:33   ` Frank Li
2024-11-01  7:12   ` Manivannan Sadhasivam
2024-11-02 11:37     ` Krzysztof Wilczyński
2024-10-17 13:20 ` [PATCH 2/2] PCI: dwc: ep: Use align addr function for dw_pcie_ep_raise_{msi,msix}_irq() Niklas Cassel
2024-10-17 15:36   ` Frank Li
2024-10-17 18:54     ` Niklas Cassel
2024-10-17 19:36       ` Frank Li
2024-10-31 20:28   ` Bjorn Helgaas
2024-10-31 22:36     ` Damien Le Moal
2024-11-01 18:25       ` Niklas Cassel [this message]
2024-11-01  7:16   ` Manivannan Sadhasivam
2024-11-02 11:41   ` Krzysztof Wilczyński
2024-10-20  0:59 ` [PATCH 0/2] PCI: dwc: ep: Minor alignment cleanups Damien Le Moal
2024-10-29 10:25 ` Niklas Cassel

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=ZyUdDqLwirSZEmvw@x1-carbon \
    --to=cassel@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=dlemoal@kernel.org \
    --cc=helgaas@kernel.org \
    --cc=jingoohan1@gmail.com \
    --cc=kw@linux.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --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: 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