Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915/gt: Warn if not in RC6 when GT is parked
Date: Tue, 11 Oct 2022 09:35:45 +0100	[thread overview]
Message-ID: <94c0d0c1-4d14-b175-52a6-44de04961eaa@linux.intel.com> (raw)
In-Reply-To: <87pmey29es.wl-ashutosh.dixit@intel.com>


On 11/10/2022 06:53, Dixit, Ashutosh wrote:
> On Mon, 10 Oct 2022 20:29:23 -0700, Ashutosh Dixit wrote:
>>
>> Some i915 modules implicitly assume that there is no user, kernel or
>> firmware activity after GT is parked. For example, PMU calculations are
>> incorrect if GT is not in RC6 when GT is parked (outside of the GT
>> wakeref). Therefore check and warn if GT is not in RC6 at the time of
>> parking the GT.
> 
> This patch has cause widespread dmesg_warn's in premerge CI so there is no
> intention of merging this. It just proves that these assumptions in PMU
> (for quantities such as frequency and RC6 residency) are incorrect and need
> to be addressed.

Yeah this probably does not make sense since I am not sure if driver 
actually controls when hardware goes into RC6.

Regards,

Tvrtko

> 
> Thanks.
> --
> Ashutosh
> 
> 
>> @@ -123,6 +125,10 @@ static int __gt_park(struct intel_wakeref *wf)
>> 		intel_display_power_put_async(i915, POWER_DOMAIN_GT_IRQ, wakeref);
>> 	}
>>
>> +	ret = intel_rc6_in_rc6(&gt->rc6, &in_rc6);
>> +	if (!ret && !in_rc6)
>> +		drm_warn_once(&i915->drm, "Parking, but GT is not in RC6!\n");
>> +
>> 	return 0;
>>   }

  reply	other threads:[~2022-10-11  8:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11  3:27 [Intel-gfx] [PATCH 0/2] Firm up gt park/unpark Ashutosh Dixit
2022-10-11  3:28 ` [Intel-gfx] [PATCH 1/2] drm/i915/gt: Don't do display work on platforms without display Ashutosh Dixit
2022-10-11  7:22   ` Jani Nikula
2022-10-11  7:34     ` Dixit, Ashutosh
2022-10-11  8:30       ` Tvrtko Ursulin
2022-10-11  8:34         ` Tvrtko Ursulin
2022-10-11  3:29 ` [Intel-gfx] [PATCH 2/2] drm/i915/gt: Warn if not in RC6 when GT is parked Ashutosh Dixit
2022-10-11  5:53   ` Dixit, Ashutosh
2022-10-11  8:35     ` Tvrtko Ursulin [this message]
2022-10-11  3:47 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Firm up gt park/unpark Patchwork
2022-10-11  4:37 ` [Intel-gfx] ✗ 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=94c0d0c1-4d14-b175-52a6-44de04961eaa@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=ashutosh.dixit@intel.com \
    --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