From: William McVicker <willmcvicker@google.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Jingoo Han" <jingoohan1@gmail.com>,
"Gustavo Pimentel" <gustavo.pimentel@synopsys.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
kernel-team@android.com, "Vidya Sagar" <vidyas@nvidia.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] PCI: dwc: drop dependency on ZONE_DMA32
Date: Thu, 11 Aug 2022 16:38:31 +0000 [thread overview]
Message-ID: <YvUwh1mFpB2WEWdw@google.com> (raw)
In-Reply-To: <YvTJzTpsWlEizEX3@infradead.org>
On 08/11/2022, Christoph Hellwig wrote:
> On Tue, Aug 09, 2022 at 06:00:49PM +0000, Will McVicker wrote:
> > Re-work the msi_msg DMA allocation logic to use dma_alloc_coherent()
> > which uses the coherent DMA mask to try and return an allocation within
> > the DMA mask limits. This allows kernel configurations that disable
> > ZONE_DMA32 to continue supporting a 32-bit DMA mask. Without this patch,
> > the PCIe host device will fail to probe when ZONE_DMA32 is disabled.
>
> > + dma_free_coherent(dev, PAGE_SIZE, pp->msi_page, pp->msi_data);
>
> Isn't msi_page a struct page * which should become a void * now?
>
> Otherwise this looks good and is what the driver should have done
> from the very beginning.
I've updated this in v3 to use dmam_alloc_coherent() and dropped msi_page
since it's not actually used. So this block is dropped now. Thanks for
taking a look though!
--Will
next prev parent reply other threads:[~2022-08-11 17:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 18:00 [PATCH v1 0/2] PCI: dwc: Add support for 64-bit MSI target addresses Will McVicker
2022-08-09 18:00 ` [PATCH v1 1/2] PCI: dwc: drop dependency on ZONE_DMA32 Will McVicker
2022-08-11 9:20 ` Christoph Hellwig
2022-08-11 16:38 ` William McVicker [this message]
2022-08-09 18:00 ` [PATCH v1 2/2] PCI: dwc: add support for 64-bit MSI target address Will McVicker
2022-08-10 17:18 ` kernel test robot
2022-08-11 9:22 ` Christoph Hellwig
2022-08-11 16:36 ` William McVicker
2022-08-11 12:32 ` kernel test robot
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=YvUwh1mFpB2WEWdw@google.com \
--to=willmcvicker@google.com \
--cc=bhelgaas@google.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=hch@infradead.org \
--cc=jingoohan1@gmail.com \
--cc=kernel-team@android.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=vidyas@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.