From: Jaroslav Kysela <perex@perex.cz>
To: Christoph Hellwig <hch@lst.de>, Takashi Iwai <tiwai@suse.de>
Cc: David Rientjes <rientjes@google.com>,
"Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>,
alsa-devel@alsa-project.org, bp@alien8.de, hch@infradead.org,
hpa@zytor.com, linux-kernel@vger.kernel.org, mingo@redhat.com,
Pavel Machek <pavel@ucw.cz>,
tglx@linutronix.de, tiwai@suse.com, x86@kernel.org
Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash
Date: Tue, 9 Jun 2020 15:16:38 +0200 [thread overview]
Message-ID: <a20ab909-bb60-8d47-0da3-122a724aecbe@perex.cz> (raw)
In-Reply-To: <20200609114955.GA2027@lst.de>
Dne 09. 06. 20 v 13:49 Christoph Hellwig napsal(a):
> On Tue, Jun 09, 2020 at 01:45:34PM +0200, Takashi Iwai wrote:
>> Yes, for the sound stuff, something below should make things working.
>> But it means that we'll lose the SG-buffer allocation and the
>> allocation of large buffers might fail on some machines.
>
> We crossed lines there. In general due to better memory compaction and
> CMA we have better chances to get larger contiguous allocations these
> days, so this might not be too much of an issue in practice.
>
But turning off the SG DMA scheme seems like a step back. Would be possible to
fix this kind of memory mapping?
Jaroslav
--
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
WARNING: multiple messages have this Message-ID (diff)
From: Jaroslav Kysela <perex@perex.cz>
To: Christoph Hellwig <hch@lst.de>, Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, x86@kernel.org,
David Rientjes <rientjes@google.com>,
linux-kernel@vger.kernel.org,
"Alex Xu \(Hello71\)" <alex_y_xu@yahoo.ca>,
tiwai@suse.com, hch@infradead.org, mingo@redhat.com,
bp@alien8.de, Pavel Machek <pavel@ucw.cz>,
hpa@zytor.com, tglx@linutronix.de
Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash
Date: Tue, 9 Jun 2020 15:16:38 +0200 [thread overview]
Message-ID: <a20ab909-bb60-8d47-0da3-122a724aecbe@perex.cz> (raw)
In-Reply-To: <20200609114955.GA2027@lst.de>
Dne 09. 06. 20 v 13:49 Christoph Hellwig napsal(a):
> On Tue, Jun 09, 2020 at 01:45:34PM +0200, Takashi Iwai wrote:
>> Yes, for the sound stuff, something below should make things working.
>> But it means that we'll lose the SG-buffer allocation and the
>> allocation of large buffers might fail on some machines.
>
> We crossed lines there. In general due to better memory compaction and
> CMA we have better chances to get larger contiguous allocations these
> days, so this might not be too much of an issue in practice.
>
But turning off the SG DMA scheme seems like a step back. Would be possible to
fix this kind of memory mapping?
Jaroslav
--
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
next prev parent reply other threads:[~2020-06-09 13:17 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 11:11 next-0519 on thinkpad x60: sound related? window manager crash Pavel Machek
2020-05-20 11:37 ` Takashi Iwai
2020-05-20 11:37 ` Takashi Iwai
2020-05-20 11:39 ` Pavel Machek
2020-05-20 11:39 ` Pavel Machek
2020-05-20 11:43 ` Takashi Iwai
2020-05-20 11:43 ` Takashi Iwai
2020-06-07 15:58 ` Alex Xu (Hello71)
2020-06-07 16:38 ` 82fef0ad811f "x86/mm: unencrypted non-blocking DMA allocations use coherent pools" was " Pavel Machek
2020-06-07 16:38 ` Pavel Machek
2020-06-07 19:41 ` David Rientjes
2020-06-07 19:41 ` David Rientjes
2020-06-07 22:53 ` Alex Xu (Hello71)
2020-06-07 22:53 ` Alex Xu (Hello71)
2020-06-08 0:57 ` David Rientjes
2020-06-08 0:57 ` David Rientjes
2020-06-08 2:13 ` Alex Xu (Hello71)
2020-06-08 2:13 ` Alex Xu (Hello71)
2020-06-08 6:19 ` Christoph Hellwig
2020-06-08 6:19 ` Christoph Hellwig
2020-06-08 13:53 ` Alex Xu (Hello71)
2020-06-08 13:53 ` Alex Xu (Hello71)
2020-06-09 2:31 ` David Rientjes
2020-06-09 2:31 ` David Rientjes
2020-06-09 5:43 ` Christoph Hellwig
2020-06-09 5:43 ` Christoph Hellwig
2020-06-09 8:05 ` Takashi Iwai
2020-06-09 8:05 ` Takashi Iwai
2020-06-09 8:43 ` Christoph Hellwig
2020-06-09 8:43 ` Christoph Hellwig
2020-06-09 9:09 ` Takashi Iwai
2020-06-09 9:09 ` Takashi Iwai
2020-06-09 9:17 ` Christoph Hellwig
2020-06-09 9:17 ` Christoph Hellwig
2020-06-09 9:31 ` Takashi Iwai
2020-06-09 9:31 ` Takashi Iwai
2020-06-09 11:02 ` Takashi Iwai
2020-06-09 11:02 ` Takashi Iwai
2020-06-09 11:31 ` Christoph Hellwig
2020-06-09 11:31 ` Christoph Hellwig
2020-06-09 11:38 ` Takashi Iwai
2020-06-09 11:38 ` Takashi Iwai
2020-06-09 11:40 ` Christoph Hellwig
2020-06-09 11:40 ` Christoph Hellwig
2020-06-09 11:45 ` Takashi Iwai
2020-06-09 11:45 ` Takashi Iwai
2020-06-09 11:49 ` Christoph Hellwig
2020-06-09 11:49 ` Christoph Hellwig
2020-06-09 13:16 ` Jaroslav Kysela [this message]
2020-06-09 13:16 ` Jaroslav Kysela
2020-06-10 5:26 ` David Rientjes
2020-06-10 5:26 ` David Rientjes
2020-06-10 7:14 ` Christoph Hellwig
2020-06-10 7:14 ` Christoph Hellwig
2020-06-09 11:47 ` Christoph Hellwig
2020-06-09 11:47 ` Christoph Hellwig
2020-06-09 15:12 ` Takashi Iwai
2020-06-09 15:12 ` Takashi Iwai
[not found] ` <<s5hr1uogtna.wl-tiwai@suse.de>
2020-06-11 14:51 ` Alex Xu (Hello71)
2020-06-11 14:51 ` Alex Xu (Hello71)
2020-06-11 17:11 ` Takashi Iwai
2020-06-11 17:11 ` Takashi Iwai
2020-06-13 16:25 ` Alex Xu (Hello71)
2020-06-13 16:25 ` Alex Xu (Hello71)
2020-06-14 9:54 ` Takashi Iwai
2020-06-14 9:54 ` Takashi Iwai
2020-06-14 12:07 ` Alex Xu (Hello71)
2020-06-14 12:07 ` Alex Xu (Hello71)
2020-06-14 15:40 ` Takashi Iwai
2020-06-14 15:40 ` Takashi Iwai
2020-06-11 14:51 ` Alex Xu (Hello71)
2020-06-11 14:51 ` Alex Xu (Hello71)
[not found] <20200520110900.GA8203@amd>
2020-05-21 7:41 ` Pavel Machek
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=a20ab909-bb60-8d47-0da3-122a724aecbe@perex.cz \
--to=perex@perex.cz \
--cc=alex_y_xu@yahoo.ca \
--cc=alsa-devel@alsa-project.org \
--cc=bp@alien8.de \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.