From: akpm@linux-foundation.org
To: boris.brezillon@free-electrons.com, airlied@linux.ie,
daniel@ffwll.ch, eric@anholt.net, iamjoonsoo.kim@lge.com,
jaewon31.kim@samsung.com, labbott@redhat.com,
mm-commits@vger.kernel.org
Subject: + cma-take-__gfp_nowarn-into-account-in-cma_alloc.patch added to -mm tree
Date: Wed, 04 Oct 2017 15:18:24 -0700 [thread overview]
Message-ID: <59d55e30.WK0ez1kfSTaMPwg8%akpm@linux-foundation.org> (raw)
The patch titled
Subject: mm/cma.c: take __GFP_NOWARN into account in cma_alloc()
has been added to the -mm tree. Its filename is
cma-take-__gfp_nowarn-into-account-in-cma_alloc.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/cma-take-__gfp_nowarn-into-account-in-cma_alloc.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/cma-take-__gfp_nowarn-into-account-in-cma_alloc.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Boris Brezillon <boris.brezillon@free-electrons.com>
Subject: mm/cma.c: take __GFP_NOWARN into account in cma_alloc()
cma_alloc() unconditionally prints an INFO message when the CMA allocation
fails. Make this message conditional on the non-presence of __GFP_NOWARN
in gfp_mask.
This patch aims at removing INFO messages that are displayed when the VC4
driver tries to allocate buffer objects. From the driver perspective an
allocation failure is acceptable, and the driver can possibly do something
to make following allocation succeed (like flushing the VC4 internal
cache).
Link: http://lkml.kernel.org/r/20171004125447.15195-1-boris.brezillon@free-electrons.com
Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
Acked-by: Laura Abbott <labbott@redhat.com>
Cc: Jaewon Kim <jaewon31.kim@samsung.com>
Cc: David Airlie <airlied@linux.ie>
Cc: Daniel Vetter <daniel@ffwll.ch>
Cc: Eric Anholt <eric@anholt.net>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/cma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN mm/cma.c~cma-take-__gfp_nowarn-into-account-in-cma_alloc mm/cma.c
--- a/mm/cma.c~cma-take-__gfp_nowarn-into-account-in-cma_alloc
+++ a/mm/cma.c
@@ -460,7 +460,7 @@ struct page *cma_alloc(struct cma *cma,
trace_cma_alloc(pfn, page, count, align);
- if (ret) {
+ if (ret && !(gfp_mask & __GFP_NOWARN)) {
pr_info("%s: alloc failed, req-size: %zu pages, ret: %d\n",
__func__, count, ret);
cma_debug_show_areas(cma);
_
Patches currently in -mm which might be from boris.brezillon@free-electrons.com are
cma-take-__gfp_nowarn-into-account-in-cma_alloc.patch
reply other threads:[~2017-10-04 22:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=59d55e30.WK0ez1kfSTaMPwg8%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=airlied@linux.ie \
--cc=boris.brezillon@free-electrons.com \
--cc=daniel@ffwll.ch \
--cc=eric@anholt.net \
--cc=iamjoonsoo.kim@lge.com \
--cc=jaewon31.kim@samsung.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.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.