From: Moritz Fischer <mdf@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: lorenzo.pieralisi@arm.com, Moritz Fischer <mdf@kernel.org>,
Will Deacon <will@kernel.org>,
guohanjun@huawei.com, sudeep.holla@arm.com,
linux-acpi@vger.kernel.org, moritzf@google.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, rjw@rjwysocki.net
Subject: Re: [PATCH v2] ACPI/IORT: Do not blindly trust DMA masks from firmware
Date: Thu, 28 Jan 2021 09:11:58 -0800 [thread overview]
Message-ID: <YBLwXgUJR4L6IiSl@epycbox.lan> (raw)
In-Reply-To: <161175296410.16506.7622624950228429208.b4-ty@arm.com>
Hi Catalin,
On Wed, Jan 27, 2021 at 01:09:36PM +0000, Catalin Marinas wrote:
> On Thu, 21 Jan 2021 17:24:19 -0800, Moritz Fischer wrote:
> > Address issue observed on real world system with suboptimal IORT table
> > where DMA masks of PCI devices would get set to 0 as result.
> >
> > iort_dma_setup() would query the root complex'/named component IORT
> > entry for a DMA mask, and use that over the one the device has been
> > configured with earlier.
> >
> > [...]
>
> Applied to arm64 (for-next/fixes), thanks!
>
> [1/1] ACPI/IORT: Do not blindly trust DMA masks from firmware
> https://git.kernel.org/arm64/c/a1df829ead58
>
> --
> Catalin
>
Should we consider this for stable, too? If so I can send an email to
stable@ once it's in Linus' tree, since I'm the one forgetting to CC
stable in the first place :)
It would be nice if at least 5.10 would get this.
Cheers,
Moritz
prev parent reply other threads:[~2021-01-28 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 1:24 [PATCH v2] ACPI/IORT: Do not blindly trust DMA masks from firmware Moritz Fischer
2021-01-22 14:42 ` Robin Murphy
2021-01-22 17:50 ` Moritz Fischer
2021-01-22 19:17 ` Robin Murphy
2021-01-22 19:43 ` Moritz Fischer
2021-01-27 11:19 ` Lorenzo Pieralisi
2021-01-27 13:09 ` Catalin Marinas
2021-01-28 17:11 ` Moritz Fischer [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=YBLwXgUJR4L6IiSl@epycbox.lan \
--to=mdf@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=guohanjun@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=moritzf@google.com \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).