From: "Sharma, Shashank" <shashank.sharma@amd.com>
To: "Michel Dänzer" <michel.daenzer@mailbox.org>,
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 18:00:26 +0200 [thread overview]
Message-ID: <c2b5d2ea-312e-3e5e-4f0a-d8ce8709cbb2@amd.com> (raw)
In-Reply-To: <9e342f6f-cfac-83df-3b03-ee1d095d27ce@mailbox.org>
On 8/2/2022 5:58 PM, Michel Dänzer wrote:
> 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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2Fmesa%2Fdrm%2F-%2Fmerge_requests&data=05%7C01%7Cshashank.sharma%40amd.com%7C50e342a42eac4d4d4fd408da749fd574%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637950527087917031%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qU41z3Hxo0jKMWgehDWLYi7r4x1QDsA%2F2KfOigj9iew%3D&reserved=0
>
>
Noted, Thanks.
Regards
Shashank
next prev parent reply other threads:[~2022-08-02 16:00 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
2022-08-02 16:00 ` Sharma, Shashank [this message]
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=c2b5d2ea-312e-3e5e-4f0a-d8ce8709cbb2@amd.com \
--to=shashank.sharma@amd.com \
--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=michel.daenzer@mailbox.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