Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
	"Jesse.zhang@amd.com" <jesse.zhang@amd.com>,
	igt-dev@lists.freedesktop.org,
	Vitaly Prosyak <vitaly.prosyak@amd.com>,
	Alex Deucher <alexander.deucher@amd.com>,
	sukhatri@amd.com
Subject: Re: [PATCH i-g-t v2 1/2] drm-uapi/amdgpu: Add queue priority and secure flags definitions
Date: Tue, 22 Apr 2025 10:21:05 +0200	[thread overview]
Message-ID: <f25bbd40-e195-46dd-b0df-d881033bd69b@amd.com> (raw)
In-Reply-To: <20250417163710.rr3j4dc7fin5ikfo@kamilkon-DESK.igk.intel.com>

Am 17.04.25 um 18:37 schrieb Kamil Konieczny:
> Hi Jesse.zhang,
> On 2025-04-17 at 16:52:46 +0800, Jesse.zhang@amd.com wrote:
>> Add UAPI definitions for queue priority levels (NORMAL_LOW, LOW, etc.)
>> and secure queue flag in amdgpu_drm.h. This matches the libdrm changes
>> in commit fdf384d4b546 ("amdgpu: add priority and secure flags for user queues").
> Please write from what tree comes this commit or
> give lore.kernel.org link.
>
> I tried to find out this on current drm-tip and failed,
> am I missing something?

This is a patch for the IGT test cases and not the Linux kernel.

It has i-g-t in the subject line and is send out on the igt-dev mailing list.

Regards,
Christian.

>
> Regards,
> Kamil
>
>> v2: In general, UAPI changes should be part of a different change and only uapi should be part of it (Sunil)
>>
>> Signed-off-by: Jesse.Zhang <Jesse.zhang@amd.com>
>> ---
>>  include/drm-uapi/amdgpu_drm.h | 12 +++++++++++-
>>  1 file changed, 11 insertions(+), 1 deletion(-)
>>
>> diff --git a/include/drm-uapi/amdgpu_drm.h b/include/drm-uapi/amdgpu_drm.h
>> index 8191d0bd0..3f4813879 100644
>> --- a/include/drm-uapi/amdgpu_drm.h
>> +++ b/include/drm-uapi/amdgpu_drm.h
>> @@ -329,6 +329,16 @@ union drm_amdgpu_ctx {
>>  #define AMDGPU_USERQ_OP_CREATE	1
>>  #define AMDGPU_USERQ_OP_FREE	2
>>  
>> +/* queue priority levels */
>> +#define AMDGPU_USERQ_CREATE_FLAGS_QUEUE_PRIORITY_MASK  0x3
>> +#define AMDGPU_USERQ_CREATE_FLAGS_QUEUE_PRIORITY_SHIFT 0
>> +#define AMDGPU_USERQ_CREATE_FLAGS_QUEUE_PRIORITY_NORMAL_LOW 0
>> +#define AMDGPU_USERQ_CREATE_FLAGS_QUEUE_PRIORITY_LOW 1
>> +#define AMDGPU_USERQ_CREATE_FLAGS_QUEUE_PRIORITY_NORMAL_HIGH 2
>> +#define AMDGPU_USERQ_CREATE_FLAGS_QUEUE_PRIORITY_HIGH 3 /* admin only */
>> +/* for queues that need access to protected content */
>> +#define AMDGPU_USERQ_CREATE_FLAGS_QUEUE_SECURE  (1 << 2)
>> +
>>  /*
>>   * This structure is a container to pass input configuration
>>   * info for all supported userqueue related operations.
>> @@ -355,7 +365,7 @@ struct drm_amdgpu_userq_in {
>>  	 * and doorbell_offset in the doorbell bo.
>>  	 */
>>  	__u32   doorbell_offset;
>> -	__u32 _pad;
>> +	__u32 flags;
>>  	/**
>>  	 * @queue_va: Virtual address of the GPU memory which holds the queue
>>  	 * object. The queue holds the workload packets.
>> -- 
>> 2.25.1
>>


  reply	other threads:[~2025-04-22  8:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17  8:52 [PATCH i-g-t v2 1/2] drm-uapi/amdgpu: Add queue priority and secure flags definitions Jesse.zhang@amd.com
2025-04-17  8:52 ` [PATCH i-g-t v2 2/2] lib/amdgpu: Implement priority and secure flags for user queues Jesse.zhang@amd.com
2025-04-17 12:44   ` Khatri, Sunil
2025-04-17 12:42 ` [PATCH i-g-t v2 1/2] drm-uapi/amdgpu: Add queue priority and secure flags definitions Khatri, Sunil
2025-04-17 13:21 ` ✗ Xe.CI.BAT: failure for series starting with [i-g-t,v2,1/2] " Patchwork
2025-04-17 13:41 ` ✓ i915.CI.BAT: success " Patchwork
2025-04-17 16:37 ` [PATCH i-g-t v2 1/2] " Kamil Konieczny
2025-04-22  8:21   ` Christian König [this message]
2025-04-18  1:12 ` ✗ i915.CI.Full: failure for series starting with [i-g-t,v2,1/2] " Patchwork
2025-04-18  3:41 ` ✗ Xe.CI.Full: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2025-04-18  2:29 [PATCH i-g-t v2 1/2] " Jesse.zhang@amd.com

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=f25bbd40-e195-46dd-b0df-d881033bd69b@amd.com \
    --to=christian.koenig@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jesse.zhang@amd.com \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=sukhatri@amd.com \
    --cc=vitaly.prosyak@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