From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Emil Velikov <emil.l.velikov@gmail.com>,
"Koenig, Christian" <Christian.Koenig@amd.com>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/amdgpu: extend AMDGPU_CTX_PRIORITY_NORMAL comment
Date: Mon, 15 Jul 2019 14:10:12 +0200 [thread overview]
Message-ID: <61429d92-640b-b092-08b2-378e28aa10e8@gmail.com> (raw)
In-Reply-To: <CACvgo51LkcF6LydoH8BCaKwK4trfrm0EQkjMricQ3b0RXcrhrA@mail.gmail.com>
Am 02.07.19 um 19:15 schrieb Emil Velikov:
> On Fri, 14 Jun 2019 at 19:02, Koenig, Christian
> <Christian.Koenig@amd.com> wrote:
>> Am 14.06.19 um 19:33 schrieb Emil Velikov:
>>> From: Emil Velikov <emil.velikov@collabora.com>
>>>
>>> Currently the AMDGPU_CTX_PRIORITY_* defines are used in both
>>> drm_amdgpu_ctx_in::priority and drm_amdgpu_sched_in::priority.
>>>
>>> Extend the comment to mention the CAP_SYS_NICE or DRM_MASTER requirement
>>> is only applicable with the former.
>>>
>>> Cc: Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
>>> Cc: Christian König <christian.koenig@amd.com>
>>> Cc: Alex Deucher <alexander.deucher@amd.com>
>>> Signed-off-by: Emil Velikov <emil.velikov@collabora.com>
>>> ---
>>> Mildly curious: why didn't one extend ctx_amdgpu_ctx instead of adding
>>> drm_amdgpu_sched? New flag + _u32 fd at the end (for the former) would
>>> have been enough (and tweaking the ioctl permission thingy).
>> The drm_amdgpu_sched is only allowed for DRM_MASTER.
>>
> Fair enough.
>
> Is the patch wrong or did it slip through the cracks? I cannot see it
> in Alex's tree.
Looks like Alex just missed this one and I was on vacation/out of office
for a while.
I've gone ahead added my rb and just pushed it.
Thanks,
Christian.
>
> -Emil
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-07-15 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 17:33 [PATCH] drm/amdgpu: extend AMDGPU_CTX_PRIORITY_NORMAL comment Emil Velikov
2019-06-14 18:02 ` Koenig, Christian
[not found] ` <b3b4b6d8-1b64-7860-88e5-ec91b9d2f711-5C7GfCeVMHo@public.gmane.org>
2019-07-02 17:15 ` Emil Velikov
2019-07-15 12:10 ` Christian König [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=61429d92-640b-b092-08b2-378e28aa10e8@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=Alexander.Deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.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