From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Harald Arnesen <harald@skogtun.org>,
Alex Xu <alex_y_xu@yahoo.ca>
Subject: Re: Intel HD Audio: sound stops working in Xen PV dom0 in >=5.17
Date: Mon, 23 Jan 2023 22:31:39 +0100 [thread overview]
Message-ID: <Y878uwEqfQ9WWPZV@mail-itl> (raw)
In-Reply-To: <878rhxpcmr.wl-tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
On Fri, Jan 20, 2023 at 02:19:08PM +0100, Takashi Iwai wrote:
> On Fri, 20 Jan 2023 13:11:34 +0100,
> Marek Marczykowski-Górecki wrote:
> >
> It's puzzling, then. The patch changes the allocation with the
> dma_alloc_coherent(), and that's what does with the Kconfig hack
> you've tested. One possible significant difference is the use of the
> DMA address.
>
> > BTW, xen_domain() will also return true on PVH/HVM domain, which should
> > not need any of this special treatment. It's PV that is weird.
>
> OK, then it can be an overkill.
>
> Below is another try: it changes the different use of the DMA buffer
> address. Let's cross fingers.
3 days update and it still works!
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-01-23 21:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Y5KPAs6f7S2dEoxR@mail-itl>
2022-12-09 8:10 ` Intel HD Audio: sound stops working in Xen PV dom0 in >=5.17 Takashi Iwai
2022-12-09 12:40 ` Marek Marczykowski-Górecki
2022-12-10 1:00 ` Marek Marczykowski-Górecki
2022-12-10 16:17 ` Marek Marczykowski-Górecki
2022-12-20 4:43 ` Marek Marczykowski-Górecki
2022-12-22 8:09 ` Takashi Iwai
2022-12-27 15:26 ` Marek Marczykowski-Górecki
2023-01-16 15:55 ` Takashi Iwai
2023-01-17 7:58 ` Takashi Iwai
2023-01-17 11:36 ` Marek Marczykowski-Górecki
2023-01-17 14:21 ` Marek Marczykowski-Górecki
2023-01-17 14:33 ` Takashi Iwai
2023-01-17 16:49 ` Marek Marczykowski-Górecki
2023-01-17 16:52 ` Takashi Iwai
2023-01-17 20:34 ` Marek Marczykowski-Górecki
2023-01-18 8:59 ` Takashi Iwai
2023-01-18 10:39 ` Marek Marczykowski-Górecki
2023-01-18 12:39 ` Takashi Iwai
2023-01-20 1:10 ` Marek Marczykowski-Górecki
2023-01-20 2:24 ` Marek Marczykowski-Górecki
2023-01-20 7:26 ` Takashi Iwai
2023-01-20 12:11 ` Marek Marczykowski-Górecki
2023-01-20 13:19 ` Takashi Iwai
2023-01-23 21:31 ` Marek Marczykowski-Górecki [this message]
2023-01-24 9:24 ` 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=Y878uwEqfQ9WWPZV@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=alex_y_xu@yahoo.ca \
--cc=alsa-devel@alsa-project.org \
--cc=harald@skogtun.org \
--cc=tiwai@suse.de \
/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