From: Michal Nazarewicz <mina86@mina86.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Vlastimil Babka <vbabka@suse.cz>,
"Robin H. Johnson" <robbat2@gentoo.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
dri-devel@lists.freedesktop.org, Joonsoo Kim <js1304@gmail.com>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: drm/radeon spamming alloc_contig_range: [xxx, yyy) PFNs busy busy
Date: Thu, 01 Dec 2016 22:02:07 +0100 [thread overview]
Message-ID: <xa1twpfjmkhc.fsf@mina86.com> (raw)
In-Reply-To: <20161201161117.GD20966@dhcp22.suse.cz>
On Thu, Dec 01 2016, Michal Hocko wrote:
> I am not familiar with this code so I cannot really argue but a quick
> look at rmem_cma_setup doesn't suggest any speicific placing or
> anything...
early_cma parses ‘cma’ command line argument which can specify where
exactly the default CMA area is to be located. Furthermore, CMA areas
can be assigned per-device (via the Device Tree IIRC).
--
Best regards
ミハウ “𝓶𝓲𝓷𝓪86” ナザレヴイツ
«If at first you don’t succeed, give up skydiving»
--
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: Michal Nazarewicz <mina86@mina86.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Vlastimil Babka <vbabka@suse.cz>,
"Robin H. Johnson" <robbat2@gentoo.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
dri-devel@lists.freedesktop.org, Joonsoo Kim <js1304@gmail.com>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: drm/radeon spamming alloc_contig_range: [xxx, yyy) PFNs busy busy
Date: Thu, 01 Dec 2016 22:02:07 +0100 [thread overview]
Message-ID: <xa1twpfjmkhc.fsf@mina86.com> (raw)
In-Reply-To: <20161201161117.GD20966@dhcp22.suse.cz>
On Thu, Dec 01 2016, Michal Hocko wrote:
> I am not familiar with this code so I cannot really argue but a quick
> look at rmem_cma_setup doesn't suggest any speicific placing or
> anything...
early_cma parses ‘cma’ command line argument which can specify where
exactly the default CMA area is to be located. Furthermore, CMA areas
can be assigned per-device (via the Device Tree IIRC).
--
Best regards
ミハウ “𝓶𝓲𝓷𝓪86” ナザレヴイツ
«If at first you don’t succeed, give up skydiving»
next prev parent reply other threads:[~2016-12-01 21:02 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 22:43 PROBLEM-PERSISTS: dmesg spam: alloc_contig_range: [XX, YY) PFNs busy Robin H. Johnson
2016-11-30 9:22 ` Michal Hocko
2016-11-30 13:08 ` Michal Nazarewicz
2016-11-30 13:28 ` Michal Hocko
2016-11-30 19:58 ` Robin H. Johnson
2016-11-30 20:19 ` drm/radeon spamming alloc_contig_range: [xxx, yyy) PFNs busy busy Robin H. Johnson
2016-11-30 21:24 ` Vlastimil Babka
2016-11-30 21:24 ` Vlastimil Babka
2016-12-01 6:21 ` Robin H. Johnson
2016-12-01 7:38 ` Vlastimil Babka
2016-12-01 7:38 ` Vlastimil Babka
2016-12-01 7:58 ` Robin H. Johnson
2016-12-01 7:58 ` Robin H. Johnson
2016-12-01 7:15 ` Michal Hocko
2016-12-01 7:15 ` Michal Hocko
2016-12-01 7:21 ` Michal Hocko
2016-12-01 7:21 ` Michal Hocko
2016-12-01 7:43 ` Vlastimil Babka
2016-12-01 7:43 ` Vlastimil Babka
2016-12-01 14:11 ` Michal Hocko
2016-12-01 14:11 ` Michal Hocko
2016-12-01 16:03 ` Michal Nazarewicz
2016-12-01 16:03 ` Michal Nazarewicz
2016-12-01 16:11 ` Michal Hocko
2016-12-01 16:11 ` Michal Hocko
2016-12-01 21:02 ` Michal Nazarewicz [this message]
2016-12-01 21:02 ` Michal Nazarewicz
2016-12-02 6:36 ` Vlastimil Babka
2016-12-02 6:36 ` Vlastimil Babka
2016-12-02 6:36 ` Vlastimil Babka
2016-12-02 10:26 ` Lucas Stach
2016-12-02 10:26 ` Lucas Stach
2016-12-02 15:17 ` Jerome Glisse
2016-12-02 15:17 ` Jerome Glisse
2016-12-02 15:17 ` Jerome Glisse
2016-12-01 1:39 ` PROBLEM-PERSISTS: dmesg spam: alloc_contig_range: [XX, YY) PFNs busy Michal Nazarewicz
2016-12-01 1:39 ` Michal Nazarewicz
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=xa1twpfjmkhc.fsf@mina86.com \
--to=mina86@mina86.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=js1304@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=mhocko@kernel.org \
--cc=robbat2@gentoo.org \
--cc=vbabka@suse.cz \
/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.