From: "Michel Dänzer" <michel.daenzer@mailbox.org>
To: Shashank Sharma <shashank.sharma@amd.com>,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Cc: Alex Deucher <alexander.deucher@amd.com>,
Marek Olsak <marek.olsak@amd.com>,
Amarnath Somalapuram <amaranath.somalapuram@amd.com>,
Christian Koenig <christian.koenig@amd.com>
Subject: Re: [PATCH] amdgpu: add context creation flags in CS IOCTL
Date: Tue, 2 Aug 2022 17:58:05 +0200 [thread overview]
Message-ID: <9e342f6f-cfac-83df-3b03-ee1d095d27ce@mailbox.org> (raw)
In-Reply-To: <20220802135558.6324-1-shashank.sharma@amd.com>
On 2022-08-02 15:55, Shashank Sharma wrote:
> This patch adds:
> - A new input parameter "flags" in the amdgpu_ctx_create2 call.
> - Some new flags defining workload type hints.
> - Some change in the caller function of amdgpu_ctx_create2, to
> accomodate this new parameter.
>
> The idea is to pass the workload hints while context creation, so
> that kernel GPU scheduler can pass this information to GPU FW, which in
> turn can adjust the GPU characterstics as per the workload type.
>
> Signed-off-by: Shashank Sharma <shashank.sharma@amd.com>
> Cc: Alex Deucher <alexander.deucher@amd.com>
> Cc: Marek Olsak <marek.olsak@amd.com>
> Cc: Christian Koenig <christian.koenig@amd.com>
> Cc: Amarnath Somalapuram <amaranath.somalapuram@amd.com>
> ---
> amdgpu/amdgpu.h | 2 ++
> amdgpu/amdgpu_cs.c | 5 ++++-
> include/drm/amdgpu_drm.h | 10 +++++++++-
See include/drm/README on how to handle changes to include/drm/*_drm.h .
Also, libdrm changes are now reviewed and merged as GitLab merge requests: https://gitlab.freedesktop.org/mesa/drm/-/merge_requests
--
Earthling Michel Dänzer | https://redhat.com
Libre software enthusiast | Mesa and Xwayland developer
next prev parent reply other threads:[~2022-08-02 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 13:55 [PATCH] amdgpu: add context creation flags in CS IOCTL Shashank Sharma
2022-08-02 15:58 ` Michel Dänzer [this message]
2022-08-02 16:00 ` Sharma, Shashank
2022-08-08 6:51 ` Somalapuram, Amaranath
2022-08-08 10:59 ` Christian König
2022-08-08 11:46 ` Sharma, Shashank
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=9e342f6f-cfac-83df-3b03-ee1d095d27ce@mailbox.org \
--to=michel.daenzer@mailbox.org \
--cc=alexander.deucher@amd.com \
--cc=amaranath.somalapuram@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=marek.olsak@amd.com \
--cc=shashank.sharma@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