From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Mark i915.reset as unsigned
Date: Wed, 05 Feb 2020 16:12:06 +0200 [thread overview]
Message-ID: <87y2th9l8p.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <158091171763.3271.18072693037503580803@skylake-alporthouse-com>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Quoting Mika Kuoppala (2020-02-05 14:03:14)
>> Chris Wilson <chris@chris-wilson.co.uk> writes:
>>
>> > We have been using '-1' to mean the maximum i915.reset level in the
>> > belief that it was unsigned... This turns out to have been a grave
>> > error, and instead of setting the default reset mechanism in igt,
>> > we have been disabling reset!
>>
>> Disabling engine reset?
>
> Hmm, Right,
>
> bool intel_has_gpu_reset(const struct intel_gt *gt)
> {
> if (!i915_modparams.reset)
> return NULL;
>
> return intel_get_gpu_reset(gt);
> }
>
> bool intel_has_reset_engine(const struct intel_gt *gt)
> {
> if (i915_modparams.reset < 2)
> return false;
>
> return INTEL_INFO(gt->i915)->has_reset_engine;
> }
>
> just engine-reset. Still that wasn't the intention when setting -1.
I was trying to correlate the graveness to the code.
Glad that we agree. With commit message pointing to per engine
reset,
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> -Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-02-05 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 12:37 [Intel-gfx] [PATCH] drm/i915: Mark i915.reset as unsigned Chris Wilson
2020-02-05 14:03 ` Mika Kuoppala
2020-02-05 14:08 ` Chris Wilson
2020-02-05 14:12 ` Mika Kuoppala [this message]
2020-02-05 18:20 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-02-08 3:50 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=87y2th9l8p.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.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