From: Takashi Iwai <tiwai@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Ariadne Conill <ariadne@ariadne.space>,
xen-devel@lists.xenproject.org, alsa-devel@alsa-project.org,
stable@vger.kernel.org
Subject: Re: [PATCH] Revert "ALSA: memalloc: Workaround for Xen PV"
Date: Mon, 16 Sep 2024 09:16:58 +0200 [thread overview]
Message-ID: <874j6g9ifp.wl-tiwai@suse.de> (raw)
In-Reply-To: <ZuK6xcmAE4sngFqk@infradead.org>
On Thu, 12 Sep 2024 11:56:21 +0200,
Christoph Hellwig wrote:
>
> On Sat, Sep 07, 2024 at 11:38:50AM +0100, Andrew Cooper wrote:
> > Individual subsystems ought not to know or care about XENPV; it's a
> > layering violation.
>
> Agreed.
>
> > If the main APIs don't behave properly, then it probably means we've got
> > a bug at a lower level (e.g. Xen SWIOTLB is a constant source of fun)
> > which is probably affecting other subsystems too.
> >
> > I think we need to re-analyse the original bug. Right now, the
> > behaviour resulting from 53466ebde is worse than what it was trying to fix.
>
> 53466ebde looks bogus to me, and the commit message doesn't even
> try to explain what bad behavior it works around. I'd also like to
> state once again that if you think something is broken about dma
> allocation or mapping helpers please Cc me and the iommu list.
>
> Most of the time it's actually the drivers doing something invalid, but
> sometimes it is a core dma layer bug or something that needs a proper
> API.
>
> Also while looking at the above commit I noticed the broken fallback
> code in snd_dma_noncontig_alloc - get_dma_ops is not for driver use,
> and starting with the code queued up for 6.12 will also return NULL
> when using dma-iommu for example.
Yes, all those are really ugly hacks and have been already removed for
6.12. Let's hope everything works as expected with it.
thanks,
Takashi
next prev parent reply other threads:[~2024-09-16 7:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 18:42 [PATCH] Revert "ALSA: memalloc: Workaround for Xen PV" Ariadne Conill
2024-09-07 7:46 ` Takashi Iwai
2024-09-07 10:38 ` Andrew Cooper
2024-09-07 10:56 ` Takashi Iwai
2024-09-09 20:02 ` Elliott Mitchell
2024-09-10 11:17 ` Takashi Iwai
2024-09-25 0:48 ` Elliott Mitchell
2024-09-12 9:56 ` Christoph Hellwig
2024-09-16 7:16 ` Takashi Iwai [this message]
2024-09-16 7:24 ` Christoph Hellwig
2024-09-16 7:30 ` Takashi Iwai
2024-09-16 7:37 ` Christoph Hellwig
2024-09-16 8:20 ` 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=874j6g9ifp.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=andrew.cooper3@citrix.com \
--cc=ariadne@ariadne.space \
--cc=hch@infradead.org \
--cc=stable@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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).