From: Yonatan Maman <ymaman@nvidia.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: nouveau@lists.freedesktop.org, Gal Shalom <GalShalom@nvidia.com>,
kherbst@redhat.com, lyude@redhat.com, dakr@redhat.com,
airlied@gmail.com, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] nouveau/dmem: Fix privileged error in copy engine channel
Date: Mon, 7 Oct 2024 15:35:09 +0300 [thread overview]
Message-ID: <c427098a-7939-4a00-b728-0e2da02d7424@nvidia.com> (raw)
In-Reply-To: <ZvqHA76iSOYJexSh@pollux>
On 30/09/2024 14:09, Danilo Krummrich wrote:
> External email: Use caution opening links or attachments
>
>
> 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
Thanks for the feedback! I will address these comments and send V2
patch-set.
>
>> ---
>> 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
>>
prev parent reply other threads:[~2024-10-07 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240923135449.356244-1-Ymaman@Nvidia.com>
[not found] ` <20240923135449.356244-3-Ymaman@Nvidia.com>
[not found] ` <ZvqJgMVBs2kAWguk@pollux>
2024-10-07 12:28 ` [PATCH 2/2] nouveau/dmem: Fix memory leak in `migrate_to_ram` upon copy error Yonatan Maman
2024-10-07 13:51 ` Danilo Krummrich
[not found] ` <20240923135449.356244-2-Ymaman@Nvidia.com>
[not found] ` <ZvqHA76iSOYJexSh@pollux>
2024-10-07 12:35 ` Yonatan Maman [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=c427098a-7939-4a00-b728-0e2da02d7424@nvidia.com \
--to=ymaman@nvidia.com \
--cc=GalShalom@nvidia.com \
--cc=airlied@gmail.com \
--cc=dakr@kernel.org \
--cc=dakr@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kherbst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®