From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH RFC] drm/i915/vlv: Ramp up gpu freq gradually
Date: Wed, 17 Jan 2018 10:31:09 +0200 [thread overview]
Message-ID: <87mv1cj38y.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <151611637090.21947.8174179182626525273@mail.alporthouse.com>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Quoting Mika Kuoppala (2018-01-16 15:21:16)
>> There is a suspicion that with aggressive upclocking, power rail
>> voltage fluctuations can disrupt c state transition, leading
>> to system hang.
>>
>> When upclocking with 4 cpu Baytrails, bring up cpus to c1 and then
>> go through bins gradually towards target frequency to give leeway
>> for hw.
>>
>> We go towards requested frequency on 1 millisecond intervals. For
>> each 1 millisecond, we increase the frequency by half of bins
>> that are in between current frequency and target.
>
> Either this is good for everyone or it is not. Doing more punit accesses
> seems counter productive though, and adds 8ms to the initial request?
Wanted to see if it is not punit access in itself but voltage rampup. We
can forget this patch as atleast with these values as it didn't survive
night.
-Mika
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-01-17 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 15:21 [PATCH RFC] drm/i915/vlv: Ramp up gpu freq gradually Mika Kuoppala
2018-01-16 15:26 ` Chris Wilson
2018-01-17 8:31 ` Mika Kuoppala [this message]
2018-01-17 9:16 ` Hans de Goede
2018-01-17 15:45 ` Ville Syrjälä
2018-01-17 15:50 ` Hans de Goede
2018-01-16 16:05 ` ✗ Fi.CI.BAT: warning for " 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=87mv1cj38y.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=hdegoede@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.