Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: alsa-devel@alsa-project.org
Cc: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Subject: [PATCH 0/2] ALSA: memalloc: Fix for Xen PV and non-IOMMU systems
Date: Tue, 24 Jan 2023 10:27:42 +0100	[thread overview]
Message-ID: <20230124092744.27370-1-tiwai@suse.de> (raw)

Hi,

this is a patch series to address the recent regression on Xen PV (and
possibly non-IOMMU) systems about the SG-buffer memory allocation.
We switched to use dma_alloc_noncontiguous() as hoped it handling
everything right, but it turned out that this doesn't work always.
So this is one step back, use the explicit SG-buffer with
dma_alloc_coherent() calls, but in a bit more optimized ways, and also
applying only for those systems.


Takashi

===

Takashi Iwai (2):
  ALSA: memalloc: Explicit SG-allocations for Xen PV and non-IOMMU
    systems
  ALSA: memalloc: Use coherent DMA allocation for fallback again

 sound/core/memalloc.c | 68 +++++++++++++++++++++++++++++++++----------
 1 file changed, 53 insertions(+), 15 deletions(-)

-- 
2.35.3


             reply	other threads:[~2023-01-24  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24  9:27 Takashi Iwai [this message]
2023-01-24  9:27 ` [PATCH 1/2] ALSA: memalloc: Explicit SG-allocations for Xen PV and non-IOMMU systems Takashi Iwai
2023-01-24  9:27 ` [PATCH 2/2] ALSA: memalloc: Use coherent DMA allocation for fallback again Takashi Iwai
2023-01-25 15:29 ` [PATCH 0/2] ALSA: memalloc: Fix for Xen PV and non-IOMMU systems Takashi Iwai
2023-01-25 15:33   ` Marek Marczykowski-Górecki

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=20230124092744.27370-1-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=marmarek@invisiblethingslab.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