All of lore.kernel.org
 help / color / mirror / Atom feed
From: Danilo Krummrich <dakr@kernel.org>
To: Yonatan Maman <Ymaman@nvidia.com>
Cc: nouveau@lists.freedesktop.org, Gal Shalom <GalShalom@nvidia.com>
Subject: Re: [PATCH 1/2] nouveau/dmem: Fix privileged error in copy engine channel
Date: Mon, 30 Sep 2024 13:09:55 +0200	[thread overview]
Message-ID: <ZvqHA76iSOYJexSh@pollux> (raw)
In-Reply-To: <20240923135449.356244-2-Ymaman@Nvidia.com>

Hi Yonatan,

On Mon, Sep 23, 2024 at 01:54:56PM +0000, Yonatan Maman wrote:
> When `nouveau_dmem_copy_one` is called, the following error occurs:
> 
> [272146.675156] nouveau 0000:06:00.0: fifo: PBDMA9: 00000004 [HCE_PRIV]
> ch 1 00000300 00003386
> 
> This indicates that a copy push command triggered a Host Copy Engine
> Privileged error on channel 1 (Copy Engine channel). To address this
> issue, modify the Copy Engine channel to allow privileged push commands
> 
> Fixes: 6de125383a5cc
> Signed-off-by: Yonatan Maman <Ymaman@Nvidia.com>
> Signed-off-by: Gal Shalom <GalShalom@Nvidia.com>

Please read [1] and use scripts/checkpatch.pl and scripts/get_maintainer.pl
before sending patches.

In particular, the 'Fixes' tag has a defined format, I recommend:

```
[core]
        abbrev = 12
[pretty]
        fixes = Fixes: %h (\"%s\")
```

in your `.gitconfig`.

Also make sure so use 'Co-developed-by' if there is a co-author; I see that this
patch is also signed off by Gal Shalom.

Please also send the patches to all relevant mailing lists and maintainers to
avoid your patches not getting the required attention.

[1] https://docs.kernel.org/process/submitting-patches.html

> ---
>  drivers/gpu/drm/nouveau/nouveau_drm.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/nouveau/nouveau_drm.c b/drivers/gpu/drm/nouveau/nouveau_drm.c
> index a58c31089613..0a75ce4c5021 100644
> --- a/drivers/gpu/drm/nouveau/nouveau_drm.c
> +++ b/drivers/gpu/drm/nouveau/nouveau_drm.c
> @@ -356,7 +356,7 @@ nouveau_accel_ce_init(struct nouveau_drm *drm)
>  		return;
>  	}
>  
> -	ret = nouveau_channel_new(drm, device, false, runm, NvDmaFB, NvDmaTT, &drm->cechan);
> +	ret = nouveau_channel_new(drm, device, true, runm, NvDmaFB, NvDmaTT, &drm->cechan);
>  	if (ret)
>  		NV_ERROR(drm, "failed to create ce channel, %d\n", ret);
>  }
> -- 
> 2.34.1
> 

  reply	other threads:[~2024-09-30 11:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-23 13:54 [PATCH 0/2] *** BUG Fix for Nouveau Memory*** Yonatan Maman
2024-09-23 13:54 ` [PATCH 1/2] nouveau/dmem: Fix privileged error in copy engine channel Yonatan Maman
2024-09-30 11:09   ` Danilo Krummrich [this message]
2024-10-07 12:35     ` Yonatan Maman
2024-09-23 13:54 ` [PATCH 2/2] nouveau/dmem: Fix memory leak in `migrate_to_ram` upon copy error Yonatan Maman
2024-09-30 11:20   ` Danilo Krummrich
2024-10-07 12:28     ` Yonatan Maman
2024-10-07 13:51       ` Danilo Krummrich
  -- strict thread matches above, loose matches on Subject: below --
2024-09-29 12:30 [PATCH 0/2] *** drm/nouveau/dmem: Fix Memory Leaking and Device Channels configuration*** Yonatan Maman
2024-09-29 12:30 ` [PATCH 1/2] nouveau/dmem: Fix privileged error in copy engine channel Yonatan Maman
2024-09-29 12:16 [PATCH 0/2] *** drm/nouveau/dmem: Fix Memory Leaking and Device Channels configuration*** Yonatan Maman
2024-09-29 12:16 ` [PATCH 1/2] nouveau/dmem: Fix privileged error in copy engine channel Yonatan Maman
2024-09-29 12:08 [PATCH 0/2] *** drm/nouveau/dmem: BUG Fixes for Nouveau DMEM*** Yonatan Maman
2024-09-29 12:08 ` [PATCH 1/2] nouveau/dmem: Fix privileged error in copy engine channel Yonatan Maman
2024-09-29 11:44 [PATCH 0/2] *** BUG Fix for Nouveau Memory*** Yonatan Maman
2024-09-29 11:44 ` [PATCH 1/2] nouveau/dmem: Fix privileged error in copy engine channel Yonatan Maman
2024-09-18 15:41 [PATCH 0/2] *** BUG Fix for Nouveau Memory*** Yonatan Maman
2024-09-18 15:41 ` [PATCH 1/2] nouveau/dmem: Fix privileged error in copy engine channel Yonatan Maman

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=ZvqHA76iSOYJexSh@pollux \
    --to=dakr@kernel.org \
    --cc=GalShalom@nvidia.com \
    --cc=Ymaman@nvidia.com \
    --cc=nouveau@lists.freedesktop.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.