From: Chuck Ebbert <cebbert.lkml@gmail.com>
To: Thomas Hellstrom <thellstrom@vmware.com>
Cc: Peter Hurley <peter@hurleysoftware.com>,
Mel Gorman <mgorman@suse.de>, Shaohua Li <shli@kernel.org>,
Rik van Riel <riel@redhat.com>,
Maarten Lankhorst <maarten.lankhorst@canonical.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Ingo Molnar <mingo@kernel.org>,
Hugh Dickens <hughd@google.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: page allocator bug in 3.16?
Date: Fri, 26 Sep 2014 05:40:05 -0500 [thread overview]
Message-ID: <20140926054005.5c7985c0@as> (raw)
In-Reply-To: <542512AD.9070304@vmware.com>
On Fri, 26 Sep 2014 09:15:57 +0200
Thomas Hellstrom <thellstrom@vmware.com> wrote:
> On 09/26/2014 01:52 AM, Peter Hurley wrote:
> > On 09/25/2014 03:35 PM, Chuck Ebbert wrote:
> >> There are six ttm patches queued for 3.16.4:
> >>
> >> drm-ttm-choose-a-pool-to-shrink-correctly-in-ttm_dma_pool_shrink_scan.patch
> >> drm-ttm-fix-handling-of-ttm_pl_flag_topdown-v2.patch
> >> drm-ttm-fix-possible-division-by-0-in-ttm_dma_pool_shrink_scan.patch
> >> drm-ttm-fix-possible-stack-overflow-by-recursive-shrinker-calls.patch
> >> drm-ttm-pass-gfp-flags-in-order-to-avoid-deadlock.patch
> >> drm-ttm-use-mutex_trylock-to-avoid-deadlock-inside-shrinker-functions.patch
> > Thanks for info, Chuck.
> >
> > Unfortunately, none of these fix TTM dma allocation doing CMA dma allocation,
> > which is the root problem.
> >
> > Regards,
> > Peter Hurley
>
> The problem is not really in TTM but in CMA, There was a guy offering to
> fix this in the CMA code but I guess he didn't probably because he
> didn't receive any feedback.
>
Yeah, the "solution" to this problem seems to be "don't enable CMA on
x86". Maybe it should even be disabled in the config system.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Chuck Ebbert <cebbert.lkml@gmail.com>
To: Thomas Hellstrom <thellstrom@vmware.com>
Cc: Peter Hurley <peter@hurleysoftware.com>,
Mel Gorman <mgorman@suse.de>, Shaohua Li <shli@kernel.org>,
Rik van Riel <riel@redhat.com>,
"Maarten Lankhorst" <maarten.lankhorst@canonical.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Ingo Molnar <mingo@kernel.org>,
Hugh Dickens <hughd@google.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: page allocator bug in 3.16?
Date: Fri, 26 Sep 2014 05:40:05 -0500 [thread overview]
Message-ID: <20140926054005.5c7985c0@as> (raw)
In-Reply-To: <542512AD.9070304@vmware.com>
On Fri, 26 Sep 2014 09:15:57 +0200
Thomas Hellstrom <thellstrom@vmware.com> wrote:
> On 09/26/2014 01:52 AM, Peter Hurley wrote:
> > On 09/25/2014 03:35 PM, Chuck Ebbert wrote:
> >> There are six ttm patches queued for 3.16.4:
> >>
> >> drm-ttm-choose-a-pool-to-shrink-correctly-in-ttm_dma_pool_shrink_scan.patch
> >> drm-ttm-fix-handling-of-ttm_pl_flag_topdown-v2.patch
> >> drm-ttm-fix-possible-division-by-0-in-ttm_dma_pool_shrink_scan.patch
> >> drm-ttm-fix-possible-stack-overflow-by-recursive-shrinker-calls.patch
> >> drm-ttm-pass-gfp-flags-in-order-to-avoid-deadlock.patch
> >> drm-ttm-use-mutex_trylock-to-avoid-deadlock-inside-shrinker-functions.patch
> > Thanks for info, Chuck.
> >
> > Unfortunately, none of these fix TTM dma allocation doing CMA dma allocation,
> > which is the root problem.
> >
> > Regards,
> > Peter Hurley
>
> The problem is not really in TTM but in CMA, There was a guy offering to
> fix this in the CMA code but I guess he didn't probably because he
> didn't receive any feedback.
>
Yeah, the "solution" to this problem seems to be "don't enable CMA on
x86". Maybe it should even be disabled in the config system.
next prev parent reply other threads:[~2014-09-26 10:40 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 18:55 page allocator bug in 3.16? Peter Hurley
2014-09-25 18:55 ` Peter Hurley
2014-09-25 18:55 ` Peter Hurley
2014-09-25 19:34 ` Maarten Lankhorst
2014-09-25 19:34 ` Maarten Lankhorst
2014-09-25 19:34 ` Maarten Lankhorst
2014-09-25 19:35 ` Chuck Ebbert
2014-09-25 19:35 ` Chuck Ebbert
2014-09-25 23:52 ` Peter Hurley
2014-09-25 23:52 ` Peter Hurley
2014-09-26 7:15 ` Thomas Hellstrom
2014-09-26 7:15 ` Thomas Hellstrom
2014-09-26 7:15 ` Thomas Hellstrom
2014-09-26 10:40 ` Chuck Ebbert [this message]
2014-09-26 10:40 ` Chuck Ebbert
2014-09-26 10:45 ` Thomas Hellstrom
2014-09-26 10:45 ` Thomas Hellstrom
2014-09-26 12:28 ` Rob Clark
2014-09-26 12:28 ` Rob Clark
2014-09-26 12:28 ` Rob Clark
2014-09-26 12:34 ` Thomas Hellstrom
2014-09-26 12:34 ` Thomas Hellstrom
2014-09-26 13:40 ` Rob Clark
2014-09-26 13:40 ` Rob Clark
2014-09-26 12:40 ` Rik van Riel
2014-09-26 12:40 ` Rik van Riel
2014-09-26 14:10 ` Peter Hurley
2014-09-26 14:10 ` Peter Hurley
2014-09-26 14:10 ` Peter Hurley
2014-09-26 15:12 ` Leann Ogasawara
2014-09-26 15:12 ` Leann Ogasawara
2014-09-27 14:15 ` Peter Hurley
2014-09-27 14:15 ` Peter Hurley
2014-09-25 20:33 ` Alex Deucher
2014-09-25 20:33 ` Alex Deucher
2014-09-25 21:10 ` Peter Hurley
2014-09-25 21:10 ` Peter Hurley
2014-10-01 9:26 ` Maarten Lankhorst
2014-10-01 9:26 ` Maarten Lankhorst
2014-09-25 20:36 ` Peter Hurley
2014-09-25 20:36 ` Peter Hurley
2014-09-25 20:36 ` Peter Hurley
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=20140926054005.5c7985c0@as \
--to=cebbert.lkml@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maarten.lankhorst@canonical.com \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peter@hurleysoftware.com \
--cc=riel@redhat.com \
--cc=shli@kernel.org \
--cc=thellstrom@vmware.com \
--cc=torvalds@linux-foundation.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.