From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/5] drm/i915/perf: allow holding preemption on filtered ctx
Date: Tue, 21 May 2019 18:52:16 +0100 [thread overview]
Message-ID: <a58ae613-a497-d713-cea7-48654bec299b@intel.com> (raw)
In-Reply-To: <155845904644.23981.2155227400765332509@skylake-alporthouse-com>
On 21/05/2019 18:17, Chris Wilson wrote:
> Quoting Lionel Landwerlin (2019-05-21 17:50:30)
>> On 21/05/2019 17:36, Chris Wilson wrote:
>>> Quoting Lionel Landwerlin (2019-05-21 15:08:52)
>>>> diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c
>>>> index f263a8374273..2ad95977f7a8 100644
>>>> --- a/drivers/gpu/drm/i915/gt/intel_lrc.c
>>>> +++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
>>>> @@ -2085,7 +2085,7 @@ static int gen9_emit_bb_start(struct i915_request *rq,
>>>> if (IS_ERR(cs))
>>>> return PTR_ERR(cs);
>>>>
>>>> - *cs++ = MI_ARB_ON_OFF | MI_ARB_ENABLE;
>>>> + *cs++ = MI_ARB_ON_OFF | rq->hw_context->arb_enable;
>>> My prediction is that this will result in this context being reset due
>>> to preemption timeouts and the context under profile being banned.
>>> Note that preemption timeouts will be the primary means for hang
>>> detection for endless batches. -Chris
>> Thanks,
>>
>> One question : how is that dealt with with compute workloads at the moment?
>> I though those where still not fully preemptable.
> Not blocking is the condition under which they get to use endless...
> compute jobs are preemptible from gen9 afaik, gen8 was problematic and so
> disabled.
>
>> I need to rework this with a more "software" approach holding on preemption.
>> Adding a condition in intel_lrc.c need_preempt() looks like the right
>> direction?
> Even less if that is our means of hangcheck.
> -Chris
>
Can we differentiate between a hangcheck & a high priority request?
If I remember correctly, we can set the hangcheck timeout somewhere in /sys.
I think it's fine to ban the context doing a perf query if it's taking
too long.
If a user runs into that scenario we can tell them to increase the timeout.
-Lionel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-05-21 17:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 14:08 [PATCH 0/5] drm/i915: Vulkan performance query support Lionel Landwerlin
2019-05-21 14:08 ` [PATCH 1/5] drm/i915/perf: introduce a versioning of the i915-perf uapi Lionel Landwerlin
2019-05-21 14:08 ` [PATCH 2/5] drm/i915/perf: allow holding preemption on filtered ctx Lionel Landwerlin
2019-05-21 16:36 ` Chris Wilson
2019-05-21 16:50 ` Lionel Landwerlin
2019-05-21 17:17 ` Chris Wilson
2019-05-21 17:52 ` Lionel Landwerlin [this message]
2019-05-24 9:28 ` Lionel Landwerlin
2019-05-24 9:42 ` Chris Wilson
2019-05-24 9:51 ` Lionel Landwerlin
2019-05-24 10:07 ` Chris Wilson
2019-05-27 22:11 ` Lionel Landwerlin
2019-05-22 4:33 ` kbuild test robot
2019-05-21 14:08 ` [PATCH 3/5] drm/i915/perf: allow for CS OA configs to be created lazily Lionel Landwerlin
2019-05-21 16:43 ` Chris Wilson
2019-05-21 16:55 ` Lionel Landwerlin
2019-05-21 14:08 ` [PATCH 4/5] drm/i915: add a new perf configuration execbuf parameter Lionel Landwerlin
2019-05-21 17:07 ` Chris Wilson
2019-05-21 17:19 ` Lionel Landwerlin
2019-05-21 17:48 ` Chris Wilson
2019-05-21 17:59 ` Lionel Landwerlin
2019-05-22 9:19 ` Lionel Landwerlin
2019-05-22 9:25 ` Chris Wilson
2019-05-22 9:30 ` Lionel Landwerlin
2019-05-28 10:52 ` Chris Wilson
2019-05-30 18:41 ` Lionel Landwerlin
2019-05-21 14:08 ` [PATCH 5/5] drm/i915: add support for perf configuration queries Lionel Landwerlin
2019-05-23 10:32 ` Dan Carpenter
2019-05-23 11:25 ` Lionel Landwerlin
2019-05-23 11:38 ` Dan Carpenter
2019-05-21 16:37 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Vulkan performance query support Patchwork
2019-05-21 16:40 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-05-21 17:26 ` ✗ Fi.CI.BAT: failure " Patchwork
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=a58ae613-a497-d713-cea7-48654bec299b@intel.com \
--to=lionel.g.landwerlin@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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