linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hillf Danton <hdanton@sina.com>
To: Alex Deucher <alexdeucher@gmail.com>,
	Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: Dave Airlie <airlied@gmail.com>,
	Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	amd-gfx list <amd-gfx@lists.freedesktop.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	"Deucher, Alexander" <Alexander.Deucher@amd.com>,
	Harry Wentland <harry.wentland@amd.com>,
	"Koenig, Christian" <Christian.Koenig@amd.com>
Subject: Re: The issue with page allocation 5.3 rc1-rc2 (seems drm culprit here)
Date: Thu,  8 Aug 2019 15:42:52 +0800	[thread overview]
Message-ID: <20190808074252.6864-1-hdanton@sina.com> (raw)


On Thu, 8 Aug 2019 13:32:06 +0800 Alex Deucher wrote:
> 
> On Wed, Aug 7, 2019 at 11:49 PM Mikhail Gavrilov wrote:
> >
> > Unfortunately error "gnome-shell: page allocation failure: order:4,
> > mode:0x40cc0(GFP_KERNEL|__GFP_COMP),
> > nodemask=(null),cpuset=/,mems_allowed=0" still happens even with
> > applying this patch.

Thanks Mikhail.

No surpring to see the warning because of kvmalloc on top of the current
kmalloc. Any other difference observed?

> I think we can just drop the kmalloc altogether.

Dropping kmalloc altogether OTOH makes the reason for the vmalloc
fallback IMO, Sir?

> How about this patch?
> 
> From: Alex Deucher <alexander.deucher@amd.com>
> Date: Thu, 8 Aug 2019 00:29:23 -0500
> Subject: [PATCH] drm/amd/display: use kvmalloc for dc_state
> 
> It's large and doesn't need contiguous memory.
> 
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> ---

Looks good to me if with a kvfree added.

>  drivers/gpu/drm/amd/display/dc/core/dc.c | 9 +++++----
>  1 file changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/gpu/drm/amd/display/dc/core/dc.c b/drivers/gpu/drm/amd/display/dc/core/dc.c
> index 252b621d93a9..ef780a4e484a 100644
> --- a/drivers/gpu/drm/amd/display/dc/core/dc.c
> +++ b/drivers/gpu/drm/amd/display/dc/core/dc.c
> @@ -23,6 +23,7 @@
>   */
>  
>  #include <linux/slab.h>
> +#include <linux/mm.h>
>  
>  #include "dm_services.h"
>  
> @@ -1183,8 +1184,8 @@ bool dc_post_update_surfaces_to_stream(struct dc *dc)
>  
>  struct dc_state *dc_create_state(struct dc *dc)
>  {
> -	struct dc_state *context = kzalloc(sizeof(struct dc_state),
> -					   GFP_KERNEL);
> +	struct dc_state *context = kvzalloc(sizeof(struct dc_state),
> +					    GFP_KERNEL);
>  
>  	if (!context)
>  		return NULL;
> @@ -1204,11 +1205,11 @@ struct dc_state *dc_create_state(struct dc *dc)
>  struct dc_state *dc_copy_state(struct dc_state *src_ctx)
>  {
>  	int i, j;
> -	struct dc_state *new_ctx = kmemdup(src_ctx,
> -			sizeof(struct dc_state), GFP_KERNEL);
> +	struct dc_state *new_ctx = kvmalloc(sizeof(struct dc_state), GFP_KERNEL);
>  
>  	if (!new_ctx)
>  		return NULL;
> +	memcpy(new_ctx, src_ctx, sizeof(struct dc_state));
>  
>  	for (i = 0; i < MAX_PIPES; i++) {
>  			struct pipe_ctx *cur_pipe = &new_ctx->res_ctx.pipe_ctx[i];
> -- 
> 2.20.1
> 


             reply	other threads:[~2019-08-08  7:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-08  7:42 Hillf Danton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-08-06  1:48 Hillf Danton
2019-08-08  3:48 ` Mikhail Gavrilov
2019-08-08  5:31   ` Alex Deucher
2019-08-08  8:12     ` Michel Dänzer
2019-08-08 14:26       ` Alex Deucher
2019-08-09 18:55         ` Mikhail Gavrilov
2019-08-10 16:08           ` Mikhail Gavrilov
2019-08-05  3:21 Hillf Danton
2019-08-05 17:14 ` Mikhail Gavrilov
2019-08-04 22:23 Mikhail Gavrilov
2019-08-05  1:03 ` Dave Airlie

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=20190808074252.6864-1-hdanton@sina.com \
    --to=hdanton@sina.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Christian.Koenig@amd.com \
    --cc=airlied@gmail.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mikhail.v.gavrilov@gmail.com \
    /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