AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andres Rodriguez <andresx7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Cc: emil.l.velikov-Re5JQEeQqe8@public.gmane.org,
	Andres Rodriguez
	<andresx7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH 2/3] headers: add new context priority parameter to amdgpu_drm.h
Date: Wed,  4 Jan 2017 19:29:34 -0500	[thread overview]
Message-ID: <20170105002935.5796-3-andresx7@gmail.com> (raw)
In-Reply-To: <20170105002935.5796-1-andresx7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

This patch is for reference only, as the corresponding kernel change is
still under review.

Signed-off-by: Andres Rodriguez <andresx7@gmail.com>
---
 include/drm/amdgpu_drm.h | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/include/drm/amdgpu_drm.h b/include/drm/amdgpu_drm.h
index 3961836..2d331ee 100644
--- a/include/drm/amdgpu_drm.h
+++ b/include/drm/amdgpu_drm.h
@@ -160,13 +160,17 @@ union drm_amdgpu_bo_list {
 /* unknown cause */
 #define AMDGPU_CTX_UNKNOWN_RESET	3
 
+/* Context priority level */
+#define AMDGPU_CTX_PRIORITY_NORMAL	0
+#define AMDGPU_CTX_PRIORITY_HIGH	1
+
 struct drm_amdgpu_ctx_in {
 	/** AMDGPU_CTX_OP_* */
 	__u32	op;
 	/** For future use, no flags defined so far */
 	__u32	flags;
 	__u32	ctx_id;
-	__u32	_pad;
+	__u32	priority;
 };
 
 union drm_amdgpu_ctx_out {
-- 
2.9.3

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  parent reply	other threads:[~2017-01-05  0:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05  0:29 [PATCH v3] libdrm changes for high priority contexts Andres Rodriguez
     [not found] ` <20170105002935.5796-1-andresx7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-01-05  0:29   ` [PATCH 1/3] headers: Sync {amdgpu,radeon}_drm.h with the kernel Andres Rodriguez
     [not found]     ` <20170105002935.5796-2-andresx7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-01-09 16:23       ` Emil Velikov
     [not found]         ` <CACvgo50x_z1XrM-V2jvYf3e3zp4muy0Wyxpimk_5zM9hof28PQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-09 17:01           ` Andres Rodriguez
     [not found]             ` <d5029218-6760-ef97-3dd6-632ad51dc966-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-01-09 18:00               ` Deucher, Alexander
     [not found]                 ` <BN6PR12MB165210337024334D288C5F42F7640-/b2+HYfkarQqUD6E6FAiowdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-01-09 18:07                   ` Andres Rodriguez
2017-01-05  0:29   ` Andres Rodriguez [this message]
     [not found]     ` <20170105002935.5796-3-andresx7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-01-09 16:28       ` [PATCH 2/3] headers: add new context priority parameter to amdgpu_drm.h Emil Velikov
     [not found]         ` <CACvgo53xrtLkCVj4xcZ7BzrsFWXJMBLMqNFkgYau3Gro-3KDjg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-09 17:04           ` Andres Rodriguez
2017-01-05  0:29   ` [PATCH 3/3] amdgpu: implement context priority for amdgpu_cs_ctx_create2 v3 Andres Rodriguez

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=20170105002935.5796-3-andresx7@gmail.com \
    --to=andresx7-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=emil.l.velikov-Re5JQEeQqe8@public.gmane.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