From: Christoph Hellwig <hch@lst.de>
To: iommu@lists.linux.dev
Cc: alsa-devel@alsa-project.org, Robin Murphy <robin.murphy@arm.com>,
Takashi Iwai <tiwai@suse.com>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: fix GFP_COMP use in noncoherent dma allocators
Date: Tue, 20 Dec 2022 09:20:07 +0100 [thread overview]
Message-ID: <20221220082009.569785-1-hch@lst.de> (raw)
Hi all,
this series fixe the regression where dma-iommu stopped clearing
GFP_COMP from noncoherent dma allocations by never requesting those
in the sound code and rejecting them in the core DMA API code.
Diffstat:
kernel/dma/mapping.c | 4 ++++
sound/core/memalloc.c | 4 ++--
2 files changed, 6 insertions(+), 2 deletions(-)
next reply other threads:[~2022-12-20 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 8:20 Christoph Hellwig [this message]
2022-12-20 8:20 ` [PATCH 1/2] ALSA: memalloc: don't use GFP_COMP for non-coherent dma allocations Christoph Hellwig
2022-12-20 8:20 ` [PATCH 2/2] dma-mapping: reject GFP_COMP for noncohernt allocaions Christoph Hellwig
2022-12-20 14:57 ` Kai Vehmanen
2022-12-21 6:57 ` Mikhail Gavrilov
2022-12-21 7:46 ` Christoph Hellwig
2022-12-20 12:27 ` fix GFP_COMP use in noncoherent dma allocators Takashi Iwai
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=20221220082009.569785-1-hch@lst.de \
--to=hch@lst.de \
--cc=alsa-devel@alsa-project.org \
--cc=iommu@lists.linux.dev \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
--cc=tiwai@suse.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).