From: Christoph Hellwig <hch@infradead.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: "Christoph Hellwig" <hch@infradead.org>,
"Will McVicker" <willmcvicker@google.com>,
"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,
"kernel test robot" <lkp@intel.com>
Subject: Re: [PATCH v5 2/2] PCI: dwc: Add support for 64-bit MSI target address
Date: Fri, 9 Sep 2022 07:47:15 -0700 [thread overview]
Message-ID: <YxtR8/X4fb9wSYEo@infradead.org> (raw)
In-Reply-To: <5bfd7d4d-d431-6321-89bc-663dcd36e930@arm.com>
On Fri, Sep 09, 2022 at 02:47:19PM +0100, Robin Murphy wrote:
> On 2022-09-09 14:29, Christoph Hellwig wrote:
> > On Thu, Aug 25, 2022 at 06:50:25PM +0000, Will McVicker wrote:
> > > Since not all devices require a 32-bit MSI address, add support to the
> > > PCIe host driver to allow setting the DMA mask to 64-bits if the 32-bit
> > > allocation fails. This allows kernels to disable ZONE_DMA32 and bounce
> > > buffering (swiotlb) without risking not being able to get a 32-bit address
> > > during DMA allocation.
> >
> > Umm. You can't just disable ZONE_DMA32. Linux absolutely requires a
> > 32-bit dma mask to work, it is in fact the implicit default.
>
> Eh, it's behind CONFIG_EXPERT, which makes it enough of a "I think I know
> what I'm doing and accept responsibility for picking up the pieces if it
> breaks" thing.
Seem like indeed on arm64 there is a way to disable it. The x86 model
is to just select it unconditionally, which I think is the right way
if we don't want to get into completely random failures.
next prev parent reply other threads:[~2022-09-09 14:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 18:50 [PATCH v5 0/2] PCI: dwc: Add support for 64-bit MSI target addresses Will McVicker
2022-08-25 18:50 ` [PATCH v5 1/2] PCI: dwc: Drop dependency on ZONE_DMA32 Will McVicker
2022-09-28 11:41 ` Serge Semin
2022-09-29 18:25 ` Robin Murphy
2022-09-29 19:32 ` Serge Semin
2022-09-30 11:01 ` Robin Murphy
2022-09-30 12:57 ` Serge Semin
2022-09-30 15:39 ` Robin Murphy
2022-09-30 17:02 ` William McVicker
2022-10-03 8:04 ` Lorenzo Pieralisi
2022-10-03 16:40 ` William McVicker
2022-10-07 22:45 ` Serge Semin
2022-08-25 18:50 ` [PATCH v5 2/2] PCI: dwc: Add support for 64-bit MSI target address Will McVicker
2022-08-25 20:59 ` Robin Murphy
2022-08-25 21:22 ` William McVicker
2022-09-09 13:29 ` Christoph Hellwig
2022-09-09 13:47 ` Robin Murphy
2022-09-09 14:47 ` Christoph Hellwig [this message]
2022-09-09 15:00 ` Robin Murphy
2022-09-28 12:05 ` Serge Semin
2022-09-28 17:52 ` William McVicker
2022-09-29 8:13 ` Lorenzo Pieralisi
2022-09-29 18:50 ` William McVicker
2022-09-29 19:00 ` Serge Semin
2022-09-30 13:46 ` Lorenzo Pieralisi
2022-09-30 14:14 ` Serge Semin
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=YxtR8/X4fb9wSYEo@infradead.org \
--to=hch@infradead.org \
--cc=bhelgaas@google.com \
--cc=gustavo.pimentel@synopsys.com \
--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=lkp@intel.com \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=vidyas@nvidia.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).