AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Grodzovsky, Andrey" <Andrey.Grodzovsky-5C7GfCeVMHo@public.gmane.org>
To: Alex Deucher
	<alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Cc: "Deucher, Alexander" <Alexander.Deucher-5C7GfCeVMHo@public.gmane.org>
Subject: Re: [PATCH] drm/amd/display: use kvmalloc for dc_state (v2)
Date: Fri, 9 Aug 2019 19:36:48 +0000	[thread overview]
Message-ID: <9cf3550a-4b0c-dfa2-d532-a1b83cd4b23b@amd.com> (raw)
In-Reply-To: <20190809185952.3656-1-alexander.deucher-5C7GfCeVMHo@public.gmane.org>

Reviewed-by: Andrey Grodzovsky <andrey.grodzovsky@amd.com>

Andrey

On 8/9/19 2:59 PM, Alex Deucher wrote:
> It's large and doesn't need contiguous memory.  Fixes
> allocation failures in some cases.
>
> v2: kvfree the memory.
>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> ---
>   drivers/gpu/drm/amd/display/dc/core/dc.c | 11 ++++++-----
>   1 file changed, 6 insertions(+), 5 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..21fb7ee17c9c 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];
> @@ -1242,7 +1243,7 @@ static void dc_state_free(struct kref *kref)
>   {
>   	struct dc_state *context = container_of(kref, struct dc_state, refcount);
>   	dc_resource_state_destruct(context);
> -	kfree(context);
> +	kvfree(context);
>   }
>   
>   void dc_release_state(struct dc_state *context)
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

      parent reply	other threads:[~2019-08-09 19:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09 18:59 [PATCH] drm/amd/display: use kvmalloc for dc_state (v2) Alex Deucher
     [not found] ` <20190809185952.3656-1-alexander.deucher-5C7GfCeVMHo@public.gmane.org>
2019-08-09 19:36   ` Grodzovsky, Andrey [this message]

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=9cf3550a-4b0c-dfa2-d532-a1b83cd4b23b@amd.com \
    --to=andrey.grodzovsky-5c7gfcevmho@public.gmane.org \
    --cc=Alexander.Deucher-5C7GfCeVMHo@public.gmane.org \
    --cc=alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox