intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Azhar Shaikh <azhar.shaikh@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Add a parameter to disable SAGV
Date: Tue, 27 Feb 2018 16:35:13 +0200	[thread overview]
Message-ID: <877eqywlem.fsf@intel.com> (raw)
In-Reply-To: <20180227003800.GF2294@intel.com>

On Mon, 26 Feb 2018, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> On Mon, Feb 26, 2018 at 03:45:51PM -0800, Azhar Shaikh wrote:
>> SAGV handling is currently broken which can result in system hangs.
>> Add a parameter to disable SAGV, till the SAGV handling is fixed.
>
> Not just handling of the limitations we have with SAGV is broken but
> also probably some hidden DBUF config issue that is worst when SAGV
> is enabled.
>
> But also the handling broken is not a good reason for the parameter
> itself. But the good part of this is the ability to debug display
> hard hangs issues with SAGV requirements.
>
> I'm in favor of the paramenter. We just need a different justification
> here.

*cringe* at adding a parameter to workaround issues.

>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=104975
>> Signed-off-by: Azhar Shaikh <azhar.shaikh@intel.com>
>> ---
>>  drivers/gpu/drm/i915/i915_params.c | 3 +++
>>  drivers/gpu/drm/i915/i915_params.h | 3 ++-
>>  drivers/gpu/drm/i915/intel_pm.c    | 2 +-
>>  3 files changed, 6 insertions(+), 2 deletions(-)
>> 
>> diff --git a/drivers/gpu/drm/i915/i915_params.c b/drivers/gpu/drm/i915/i915_params.c
>> index 08108ce5be21..6aede52240b0 100644
>> --- a/drivers/gpu/drm/i915/i915_params.c
>> +++ b/drivers/gpu/drm/i915/i915_params.c
>> @@ -167,6 +167,9 @@ struct i915_params i915_modparams __read_mostly = {
>>  i915_param_named_unsafe(enable_dp_mst, bool, 0600,
>>  	"Enable multi-stream transport (MST) for new DisplayPort sinks. (default: true)");
>>  
>> +i915_param_named_unsafe(disable_sagv, bool, 0600,
>> +	"Disable SAGV (default: false)");
>> +
>
> I understand that SAGV is default to enable and enabled by BIOS so we
> actually need to disable it.
>
> However the name will cause the same old confusion as disable power well disable....
>
> So I'm in favor of bool i915.enable_sagv defaults to enable
> and use i915.enable_sagv=0 when we need to disable it.

Agreed, if you must use a parameter.

BR,
Jani.



-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-02-27 14:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26 23:45 [PATCH] drm/i915: Add a parameter to disable SAGV Azhar Shaikh
2018-02-27  0:07 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-02-27  0:38 ` [PATCH] " Rodrigo Vivi
2018-02-27 14:35   ` Jani Nikula [this message]
2018-03-01 19:58     ` *cringe* at adding a parameter to workaround issues Marc Herbert
2018-03-02 14:23       ` Jani Nikula
2018-02-27  3:30 ` ✓ Fi.CI.IGT: success for drm/i915: Add a parameter to disable SAGV 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=877eqywlem.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=azhar.shaikh@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.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;
as well as URLs for NNTP newsgroup(s).