From: Helen Koike <helen.koike@collabora.com>
To: "André Almeida" <andrealmeid@igalia.com>,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Cc: pierre-eric.pelloux-prayer@amd.com,
"'Marek Olšák'" <maraeo@gmail.com>,
kernel-dev@igalia.com, alexander.deucher@amd.com,
christian.koenig@amd.com
Subject: Re: [PATCH v2 0/2] Merge all debug module parameters
Date: Thu, 31 Aug 2023 11:02:26 -0300 [thread overview]
Message-ID: <37e21200-f294-2768-ed2e-cdadfc6d17fc@collabora.com> (raw)
In-Reply-To: <20230830220808.421935-1-andrealmeid@igalia.com>
Hi André,
Thanks for your patches.
On 30/08/2023 19:08, André Almeida wrote:
> As suggested by Christian at [0], this patchset merges all debug modules
> parameters and creates a new one for disabling soft recovery:
>
>> Maybe we can overload the amdgpu_gpu_recovery module option with this.
>> Or even better merge all the developer module parameter into a
>> amdgpu_debug option. This way it should be pretty obvious that this
>> isn't meant to be used by someone who doesn't know how to use it.
>
> [0] https://lore.kernel.org/dri-devel/55f69184-1aa2-55d6-4a10-1560d75c7324@amd.com/
Would you mind to test your patchset with drm-ci ? There is an amdgpu
test there and I would love to get your feedback of the ci.
You basically just need to apply the ci patch which is available on
https://cgit.freedesktop.org/drm/drm/commit/?h=topic/drm-ci&id=0119c894ab0dc468bcb03f28063239c0a4cf970f
There are instruction on the docs, but in short: to configure it, you
push your branch to gitlab.freedesktop.org, go to the settings and
change the CI/CD configuration file from .gitlab-ci.yml to
drivers/gpu/drm/ci/gitlab-ci.yml, and you can trigger a pipeline on your
branch to get tests running.
Thank you!
Helen
>
> Changelog:
> - drop old module params
> - use BIT() macros
> - replace global var with adev-> vars
> v1: https://lore.kernel.org/lkml/20230824162505.173399-1-andrealmeid@igalia.com/
>
> André Almeida (2):
> drm/amdgpu: Merge debug module parameters
> drm/amdgpu: Create an option to disable soft recovery
>
> drivers/gpu/drm/amd/amdgpu/amdgpu.h | 5 +++
> drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 2 +-
> drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 54 +++++++++++++++---------
> drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c | 2 +-
> drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c | 6 ++-
> drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 2 +-
> drivers/gpu/drm/amd/amdkfd/kfd_chardev.c | 2 +-
> drivers/gpu/drm/amd/amdkfd/kfd_crat.c | 2 +-
> drivers/gpu/drm/amd/include/amd_shared.h | 9 ++++
> 9 files changed, 58 insertions(+), 26 deletions(-)
>
prev parent reply other threads:[~2023-08-31 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 22:08 André Almeida
2023-08-30 22:08 ` [PATCH v2 1/2] drm/amdgpu: Merge " André Almeida
2023-08-31 6:29 ` Christian König
2023-08-31 18:10 ` Felix Kuehling
2023-08-30 22:08 ` [PATCH v2 2/2] drm/amdgpu: Create an option to disable soft recovery André Almeida
2023-08-31 6:31 ` Christian König
2023-08-31 14:02 ` Helen Koike [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=37e21200-f294-2768-ed2e-cdadfc6d17fc@collabora.com \
--to=helen.koike@collabora.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andrealmeid@igalia.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-dev@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maraeo@gmail.com \
--cc=pierre-eric.pelloux-prayer@amd.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
all inboxes | Powered by JetHome®