== Series Details ==
Series: drm/i915/cnl: WaRsUseTimeoutMode
URL : https://patchwork.freedesktop.org/series/29185/
State : success
== Summary ==
Series 29185v1 drm/i915/cnl: WaRsUseTimeoutMode
https://patchwork.freedesktop.org/api/1.0/series/29185/revisions/1/mbox/
Test kms_flip:
Sub
Apparently RC6 residency is lower than expected
with EI mode for most of the cases on CNL A0, B0 and C0.
This Wa doesn't solve our lower residency, but I
believe it is better to have it since EI is not
expected to work by HW engineers anyways.
Cc: David Weinehall
Cc: Mika Kuoppala
Signed-off-by
== Series Details ==
Series: drm/i915/cnl: WaForceContextSaveRestoreNonCoherent
URL : https://patchwork.freedesktop.org/series/29184/
State : success
== Summary ==
Series 29184v1 drm/i915/cnl: WaForceContextSaveRestoreNonCoherent
https://patchwork.freedesktop.org/api/1.0/series/29184/revisions
To avoid a potential hang condition with TLB invalidation
we need to enable masked bit 5 of MMIO 0xE5F0 at boot.
Same workaround was in place for previous platforms,
but the change for CNL is more on the register offset.
But also BSpec doesn't mention the bit 15 as set on gen9
platforms and mark b
On Tue, 22 Aug 2017 14:53:25 +0100 Chris Wilson
wrote:
> shrink_slab() allows us to report back the number of objects we
> successfully scanned (out of the target shrinkctl->nr_to_scan). As
> report the number of pages owned by each GEM object as a separate item
> to the shrinker, we cannot prec
== Series Details ==
Series: drm/i915/cnl: WaPushConstantDereferenceHoldDisable
URL : https://patchwork.freedesktop.org/series/29182/
State : success
== Summary ==
Series 29182v1 drm/i915/cnl: WaPushConstantDereferenceHoldDisable
https://patchwork.freedesktop.org/api/1.0/series/29182/revisions
On Tue, 2017-08-22 at 15:15 -0700, Oscar Mateo wrote:
> Disable deref enhancement logic.
Could we add a bit more of info here?
like that fixes some CS hangs on 3D Push Constant dispatches?
with a bit more info feel free to add
Reviewed-by: Rodrigo Vivi
I checked the spec and chicken reg. Also
Disable deref enhancement logic.
Cc: Rodrigo Vivi
Cc: Mika Kuoppala
Signed-off-by: Oscar Mateo
---
drivers/gpu/drm/i915/i915_reg.h| 1 +
drivers/gpu/drm/i915/intel_engine_cs.c | 3 +++
2 files changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915
Quoting Chris Wilson (2017-08-22 18:38:28)
> We use WC pages for coherent writes into the ppGTT on !llc
> architectures. However, to create a WC page requires a stop_machine(),
> i.e. is very slow. To compensate we currently keep a per-vm cache of
> recently freed pages, but we still see the slow s
== Series Details ==
Series: Introduce private PAT management
URL : https://patchwork.freedesktop.org/series/29166/
State : success
== Summary ==
Series 29166v1 Introduce private PAT management
https://patchwork.freedesktop.org/api/1.0/series/29166/revisions/1/mbox/
Test kms_cursor_legacy:
How about I don't export "reserve" APIs in the next version? The "reserve"
stuff is totally for init and keeping current logic unchanged. I'm scared of
regression. :(
-Original Message-
From: Chris Wilson [mailto:ch...@chris-wilson.co.uk]
Sent: Tuesday, August 22, 2017 9:08 PM
To: Wang,
On Mon, Aug 21, 2017 at 5:09 PM, Pandiyan, Dhinakaran
wrote:
> On Mon, 2017-08-21 at 16:50 -0700, Rodrigo Vivi wrote:
>> Coffe Lake CPU on Kaby Lake PCH is possible.
>
> Typo ^
fixed when merging on dinq.
>
>> It does exist, and it does work.
>>
>> The only missed case was this warning here noti
== Series Details ==
Series: drm/i915: Keep a small stash of preallocated WC pages (rev2)
URL : https://patchwork.freedesktop.org/series/27622/
State : success
== Summary ==
Series 27622v2 drm/i915: Keep a small stash of preallocated WC pages
https://patchwork.freedesktop.org/api/1.0/series/27
The "reserved" PPAT indexes is for keeping current i915 logics unchanged since
I don't want to cause regression. I can remove "reserved" PPAT indexes actually.
-Original Message-
From: intel-gvt-dev [mailto:intel-gvt-dev-boun...@lists.freedesktop.org] On
Behalf Of Chris Wilson
Sent: Tues
On Sat, Aug 12, 2017 at 02:15:13AM +, Rogozhkin, Dmitry V wrote:
> $ perf stat -e instructions,i915/rcs0-busy/ workload.sh
> <... wrokload.sh output...>
>
> Performance counter stats for 'workload.sh':
> 1,204,616,268 instructions
> 0 i915/rcs0-busy/
>
>
Let's start refreshing qf a bit by introducing
subcommand and aliases like dim.
The goal is to have an standardized qf and dim
where both have same style, documentation and
also that is in a format that we can easily
introduce to make check.
Actually all new code here is a simple copy
from dim di
On Tue, Aug 22, 2017 at 12:33 AM, Jani Nikula wrote:
> On Mon, 21 Aug 2017, Rodrigo Vivi wrote:
>> Soon we will need to extend qf for very specific
>> usages of our internal maintenance and rebase bot.
>>
>> So instead of creating yet another config file
>> let's use the existent one.
>
> I think
== Series Details ==
Series: series starting with [1/6] drm/i915/lrc: Clarify the format of the
context image
URL : https://patchwork.freedesktop.org/series/29163/
State : success
== Summary ==
Series 29163v1 series starting with [1/6] drm/i915/lrc: Clarify the format of
the context image
ht
Quoting Chris Wilson (2017-08-22 19:01:11)
> Quoting Zhi Wang (2017-08-23 02:44:12)
> > The private PAT management is to support both static and dynamic PPAT
> > entry manipulation. During the initialization, the PPAT indexes with
> > specific PPAT values could be reserved and set by intel_ppat_res
Quoting Zhi Wang (2017-08-23 02:44:12)
> The private PAT management is to support both static and dynamic PPAT
> entry manipulation. During the initialization, the PPAT indexes with
> specific PPAT values could be reserved and set by intel_ppat_reserve.
> The unused PPAT entries can be allocated/fr
On Tue, Aug 22, 2017 at 12:36 AM, Daniel Vetter wrote:
> On Tue, Aug 22, 2017 at 08:55:33AM +0200, Daniel Vetter wrote:
>> On Mon, Aug 21, 2017 at 01:10:51PM -0700, Rodrigo Vivi wrote:
>> > These sequences here are already covered by `qf git` subcommand.
>> > I double checked and confirmed that ou
The private PAT management is to support both static and dynamic PPAT
entry manipulation. During the initialization, the PPAT indexes with
specific PPAT values could be reserved and set by intel_ppat_reserve.
The unused PPAT entries can be allocated/freed later at runtime. Two
APIs are introduced f
This patchset introduces private PPAT managment which enables dynamically
configuring PPAT at runtime. The previous static PPAT configuration is
kept unchanged.
More background of this patchset can be found at:
https://lists.freedesktop.org/archives/intel-gfx/2017-August/135415.html
v2:
- Rewrite
The previous static PPAT configuration for each platform is kept unchanged
and now configured through intel_ppat_reserve(). Also the PPAT feature of
each platform is described in intel PPAT instance during the initialization
and related callbacks which supports the PPAT management framework will be
Factor out setup_private_pat() for introducing the following patches.
Signed-off-by: Zhi Wang
---
drivers/gpu/drm/i915/i915_gem_gtt.c | 20
1 file changed, 12 insertions(+), 8 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_gem_gtt.c
b/drivers/gpu/drm/i915/i915_gem_gtt
The private PAT management is to support both static and dynamic PPAT
entry manipulation. During the initialization, the PPAT indexes with
specific PPAT values could be reserved and set by intel_ppat_reserve.
The unused PPAT entries can be allocated/freed later at runtime. Two
APIs are introduced f
We use WC pages for coherent writes into the ppGTT on !llc
architectures. However, to create a WC page requires a stop_machine(),
i.e. is very slow. To compensate we currently keep a per-vm cache of
recently freed pages, but we still see the slow startup of new contexts.
We can amoritize that cost
We use WC pages for coherent writes into the ppGTT on !llc
architectures. However, to create a WC page requires a stop_machine(),
i.e. is very slow. To compensate we currently keep a per-vm cache of
recently freed pages, but we still see the slow startup of new contexts.
We can amoritize that cost
---
integration-manifest | 22 ++
1 file changed, 22 insertions(+)
create mode 100644 integration-manifest
diff --git a/integration-manifest b/integration-manifest
new file mode 100644
index ..7bc477a0f3da
--- /dev/null
+++ b/integration-manifest
@@ -0,0 +1,22 @@
== Series Details ==
Series: drm/i915/edp: Be less aggressive about changing link config on eDP
(rev3)
URL : https://patchwork.freedesktop.org/series/28588/
State : success
== Summary ==
Series 28588v3 drm/i915/edp: Be less aggressive about changing link config on
eDP
https://patchwork.freed
r-b'd and pushed, thanks!
On Tue, 2017-08-22 at 11:26 +0300, Paul Kocialkowski wrote:
> This uses the dedicated HAVE_AUDIO conditional, that depends on both
> ALSA and GSL, for wrapping the audio test. This makes the wrapping
> consistent with what is done for the chamelium test.
>
> Signed-off-b
The engine also provides a mirror of the CSB write pointer in the HWSP,
but not of our read pointer. To take advantage of this we need to
remember where we read up to on the last interrupt and continue off from
there. This poses a problem following a reset, as we don't know where
the hw will start
The engine provides a mirror of the CSB in the HWSP. If we use the
cacheable reads from the HWSP, we can shave off a few mmio reads per
context-switch interrupt (which are quite frequent!). Just removing a
couple of mmio is not enough to actually reduce any latency, but a small
reduction in overall
At the time of commit 1f767e02d69f ("drm/i915: HWS must be in the
mappable region for g33"), drm_mm insertion would often default to
placing a new object high in the zone forcing us to specify that certain
HWSP must be bound within the low mappable region. Since then, drm_mm
has gained more finesse
From: Daniele Ceraolo Spurio
On gen8+ we're currently using the PPHWSP of the kernel ctx as the
global HWSP. However, when the kernel ctx gets submitted (e.g. from
__intel_autoenable_gt_powersave) the HW will use that page as both
HWSP and PPHWSP. This causes a conflict in the register arena of t
From: Michel Thierry
Using the HWSP ggtt_offset to get the lrca offset is only correct if the
HWSP happens to be before it (when we reuse the PPHWSP of the kernel
context as the engine HWSP). Instead of making this assumption, get the
lrca offset from the kernel_context engine state.
And while l
Just sending so I can see if the farm's kbl (or other execlist boxes)
have any of the same symptoms as Mika.
-Chris
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
From: Michel Thierry
Not only the context image consist of two parts (the PPHWSP, and the
logical context state), but we also allocate a header at the start of
for sharing data with GuC. Thus every lrc looks like this:
| [guc] | [hwsp] [logical state] |
|<- our header ->|<- context
== Series Details ==
Series: Add retries for dp dual mode reads
URL : https://patchwork.freedesktop.org/series/29155/
State : success
== Summary ==
Series 29155v1 Add retries for dp dual mode reads
https://patchwork.freedesktop.org/api/1.0/series/29155/revisions/1/mbox/
Test gem_exec_suspend:
Quoting Ville Syrjälä (2017-08-22 18:02:04)
> On Mon, Aug 21, 2017 at 04:54:21PM +0100, Chris Wilson wrote:
> > Quoting Chris Wilson (2017-08-17 13:37:06)
> > > If we miss the current vblank because the gpu was busy, that may cause a
> > > jitter as the frame rate temporarily drops. We try to limit
On Mon, Aug 21, 2017 at 04:54:21PM +0100, Chris Wilson wrote:
> Quoting Chris Wilson (2017-08-17 13:37:06)
> > If we miss the current vblank because the gpu was busy, that may cause a
> > jitter as the frame rate temporarily drops. We try to limit the impact
> > of this by then boosting the GPU clo
On Tue, Aug 22, 2017 at 12:22 AM, Jani Nikula wrote:
> On Mon, 21 Aug 2017, Rodrigo Vivi wrote:
>> So far we could use *dim* to apply a whole series
>> in a mbox, but only the very last patch was receiving
>> all the checks and patchwork link.
>>
>> So this patch remove this limitation by using g
So far we could use *dim* to apply a whole series
in a mbox, but only the very last patch was receiving
all the checks and patchwork link.
So this patch remove this limitation by using git mailsplit
to split the mbox and than use git am and checks individually
on each patch.
v2: a. Don't loop wit
Hi All,
When I last send this patch not everyone was enthusiastic about this
patch. As already mentioned in the v2 discussion, solving this in userspace
is not really feasible since there is no single place to fix it there, it
will need fixing in at least 6 different places from the top of my head
On some (Bay Trail) devices the LCD panel is mounted upside-down.
This commit uses the code to read back the initial rotation of the
primary plane in get_initial_plane_config from Ville Syrjala's
"drm/fb-helper: Inherit rotation wip" patch and when re-using the
initial fb it stores that in intel_c
This set of changes has some history to them. There were several attempts
to add what was called "fast link training" to i915, which actually wasn't
fast link training as per the DP spec. These changes were:
commit 5fa836a9d859 ("drm/i915: DP link training optimization")
commit 4e96c97742f4 ("dr
On Mon, Aug 21, 2017 at 11:27:37PM +, Vivi, Rodrigo wrote:
> On Mon, 2017-08-21 at 14:03 -0700, Jim Bride wrote:
> > This set of changes has some history to them. There were several attempts
> > to add what was called "fast link training" to i915, which actually wasn't
> > fast link training a
On my own workflow I was missing a way to download mboxes
directly from patchwork with the patchwork id. So my first
reflex was to modify dim to fulfil my needs. However that
was increasing dim in complexity and dependencies and leaving
that messy.
That was when Jani suggested me the dimrc extensi
merged to dinq. thanks for the patches and review
On Tue, Aug 22, 2017 at 7:44 AM, Ville Syrjälä
wrote:
> On Mon, Aug 21, 2017 at 05:03:55PM -0700, Rodrigo Vivi wrote:
>> From: Paulo Zanoni
>>
>> Make it a little less magical and a little simpler and more hardcoded
>> so we don't end up with an
On 22 August 2017 at 15:56, Lionel Landwerlin
wrote:
> On 10/08/17 14:15, Matthew Auld wrote:
>
> On 4 August 2017 at 12:20, Lionel Landwerlin
> wrote:
>
> New issues that were discovered while making the tests work on Gen8+ :
>
> - we need to measure timings between periodic reports and discard
Quoting Szwichtenberg, Radoslaw (2017-08-18 09:50:35)
> On Fri, 2017-08-18 at 08:54 +0100, Chris Wilson wrote:
> > Quoting Chris Wilson (2017-08-17 13:37:06)
> > > If we miss the current vblank because the gpu was busy, that may cause a
> > > jitter as the frame rate temporarily drops. We try to li
Our current logic to read LSPCON's current mode, stops retries and
breaks wait-loop, if it gets LSPCON_MODE_INVALID as return from the
core function. This doesn't allow us to try reading the mode again.
This patch removes this condition and allows retries reading
the currnt mode until timeout.
Th
From the CI builds, its been observed that during a driver
reload/insert, dp dual mode read function sometimes fails to
read from dual mode devices (like LSPCON) over i2c-over-aux
channel.
This patch:
- adds some delay and few retries, allowing a scope for these
devices to settle down and respon
Some of the DP dual mode devices (like LSPCON) need some time
to settle down, on specific platfomrs. Its been observed during
IGT CI runs that some of the KBL boards show some i2c-over-aux
failures when driver module is re-inserted or re-loaded.
This patch series adds some retries at various dp_du
== Series Details ==
Series: drm/i915: Boost GPU clocks if we miss the pageflip's vblank (rev2)
URL : https://patchwork.freedesktop.org/series/28921/
State : success
== Summary ==
Series 28921v2 drm/i915: Boost GPU clocks if we miss the pageflip's vblank
https://patchwork.freedesktop.org/api/1
Regards
Shashank
On 8/22/2017 8:57 PM, Jani Nikula wrote:
On Tue, 22 Aug 2017, Shashank Sharma wrote:
It's an observation during some CI tests that few LSPCON chips
respond slow while system is under load, and need some delay
while reading current mode status using i2c-over-aux channel.
Thi
If we miss the current vblank because the gpu was busy, that may cause a
jitter as the frame rate temporarily drops. We try to limit the impact
of this by then boosting the GPU clock to deliver the frame as quickly
as possible. Originally done in commit 6ad790c0f5ac ("drm/i915: Boost GPU
frequency
On Tue, 22 Aug 2017, Shashank Sharma wrote:
> It's an observation during some CI tests that few LSPCON chips
> respond slow while system is under load, and need some delay
> while reading current mode status using i2c-over-aux channel.
>
> This patch:
> - Adds few retries and delays before declari
On 22 August 2017 at 15:23, Chris Wilson wrote:
> Quoting Chris Wilson (2017-08-22 15:21:10)
>> Quoting Matthew Auld (2017-08-21 19:34:40)
>> > Some more improvements as per Chris' comments.
>> >
>> > Matthew Auld (23):
>> > mm/shmem: introduce shmem_file_setup_with_mnt
>> > drm/i915: introduc
== Series Details ==
Series: Add retries for DP dual mode devices
URL : https://patchwork.freedesktop.org/series/29146/
State : success
== Summary ==
Series 29146v1 Add retries for DP dual mode devices
https://patchwork.freedesktop.org/api/1.0/series/29146/revisions/1/mbox/
Test gem_exec_flus
On Fri, Aug 18, 2017 at 04:49:50PM +0300, ville.syrj...@linux.intel.com wrote:
> From: Ville Syrjälä
>
> A rebased reposting of the dig_port infoframe series.
>
> Notable changes since last time:
> * Dealt with the new intel_sdvo_connector_state
> * Annotated the SDP types with the DP spec versi
Regards
Shashank
On 8/22/2017 8:24 PM, Imre Deak wrote:
On Tue, Aug 22, 2017 at 08:23:49PM +0530, Shashank Sharma wrote:
It's an observation during some CI tests that few LSPCON chips
respond slow while system is under load, and need some delay
while reading current mode status using i2c-over
On 10/08/17 14:15, Matthew Auld wrote:
On 4 August 2017 at 12:20, Lionel Landwerlin
wrote:
New issues that were discovered while making the tests work on Gen8+ :
- we need to measure timings between periodic reports and discard all
other kind of reports
- it seems periodicity of the
On Tue, Aug 22, 2017 at 08:23:49PM +0530, Shashank Sharma wrote:
> It's an observation during some CI tests that few LSPCON chips
> respond slow while system is under load, and need some delay
> while reading current mode status using i2c-over-aux channel.
>
> This patch:
> - Adds few retries and
Some of the DP dual mode devices (like LSPCON) need some time
to settle down, on specific platfomrs. Its been observed during
IGT CI runs that some of the KBL boards show some i2c-over-aux
failures when driver module is re-inserted or re-loaded.
This patch series adds some retries at various dp_du
It's an observation during some CI tests that few LSPCON chips
respond slow while system is under load, and need some delay
while reading current mode status using i2c-over-aux channel.
This patch:
- Adds few retries and delays before declaring a read
failure from LSPCON hardware.
- Changes the
From the CI builds, its been observed that during a driver
reload/insert, dp dual mode read function sometimes fails to
read from dual mode devices (like LSPCON) over i2c-over-aux
channel. This patch adds some delay and few retries, allowing
a scope for these devices to settle down.
V3: Introduced
Our current logic to read LSPCON's current mode, stops retries and
breaks wait-loop, if it gets LSPCON_MODE_INVALID as return from the
core function. This doesn't allow us to try reading the mode again.
This patch removes this condition and allows retries reading
the currnt mode until timeout.
Th
== Series Details ==
Series: drm/i915: Make infoframe code available to (e)DP ports (rev4)
URL : https://patchwork.freedesktop.org/series/8183/
State : success
== Summary ==
Series 8183v4 drm/i915: Make infoframe code available to (e)DP ports
https://patchwork.freedesktop.org/api/1.0/series/81
On Mon, Aug 21, 2017 at 05:03:55PM -0700, Rodrigo Vivi wrote:
> From: Paulo Zanoni
>
> Make it a little less magical and a little simpler and more hardcoded
> so we don't end up with an array that's composed mostly of empty
> entries.
>
> v2: Add an enum for the voltage+register values (Ville).
Quoting Chris Wilson (2017-08-22 15:21:10)
> Quoting Matthew Auld (2017-08-21 19:34:40)
> > Some more improvements as per Chris' comments.
> >
> > Matthew Auld (23):
> > mm/shmem: introduce shmem_file_setup_with_mnt
> > drm/i915: introduce simple gemfs
> > drm/i915/gemfs: enable THP
> > dr
Quoting Matthew Auld (2017-08-21 19:34:40)
> Some more improvements as per Chris' comments.
>
> Matthew Auld (23):
> mm/shmem: introduce shmem_file_setup_with_mnt
> drm/i915: introduce simple gemfs
> drm/i915/gemfs: enable THP
> drm/i915: introduce page_size_mask to dev_info
> drm/i915:
From: Ville Syrjälä
Disabling the video DIP when shutting the port down seems like a good
idea.
Bspec says:
"When disabling both the DIP port and DIP transmission,
first disable the port and then disable DIP."
and
"Restriction : GCP is only supported with HDMI when the bits per color is
not eq
== Series Details ==
Series: igt/pm_rpm: Use libc 'ftw' rather than opencoding our own filetree walk
URL : https://patchwork.freedesktop.org/series/29141/
State : success
== Summary ==
IGT patchset tested on top of latest successful build
4524a8951348a31ae5dabfc4c69f2a835034ec3e tests: Introdu
Quoting Lionel Landwerlin (2017-08-22 14:48:12)
> On 22/08/17 14:28, Chris Wilson wrote:
> > Quoting Lionel Landwerlin (2017-08-22 14:11:07)
> >> On 22/08/17 12:59, Chris Wilson wrote:
> >>> Quoting Lionel Landwerlin (2017-08-22 12:45:47)
> On 08/08/17 15:21, Matthew Auld wrote:
> > On 4 A
Some shrinkers may only be able to free a bunch of objects at a time, and
so free more than the requested nr_to_scan in one pass. Whilst other
shrinkers may find themselves even unable to scan as many objects as
they counted, and so underreport. Account for the extra freed/scanned
objects against t
shrink_slab() allows us to report back the number of objects we
successfully scanned (out of the target shrinkctl->nr_to_scan). As
report the number of pages owned by each GEM object as a separate item
to the shrinker, we cannot precisely control the number of shrinker
objects we scan on each pass;
On 22/08/17 14:28, Chris Wilson wrote:
Quoting Lionel Landwerlin (2017-08-22 14:11:07)
On 22/08/17 12:59, Chris Wilson wrote:
Quoting Lionel Landwerlin (2017-08-22 12:45:47)
On 08/08/17 15:21, Matthew Auld wrote:
On 4 August 2017 at 12:20, Lionel Landwerlin
wrote:
static void
@@ -1336,6
On 04/08/17 12:39, Chris Wilson wrote:
Quoting Lionel Landwerlin (2017-08-04 12:20:30)
When debugging unstable tests on new platforms we currently we don't
cleanup everything well in between different tests. Since only a
single OA stream fd can be opened at a time, having the stream_fd as a
glob
Quoting Lionel Landwerlin (2017-08-22 14:11:07)
> On 22/08/17 12:59, Chris Wilson wrote:
> > Quoting Lionel Landwerlin (2017-08-22 12:45:47)
> >> On 08/08/17 15:21, Matthew Auld wrote:
> >>> On 4 August 2017 at 12:20, Lionel Landwerlin
> >>> wrote:
> static void
> @@ -1336,6 +1504,66
+ Sean
On Mon, 2017-08-21 at 18:16 +0200, Daniel Vetter wrote:
> On Sat, Aug 19, 2017 at 01:05:58PM +0100, Chris Wilson wrote:
> > This is the same bug as we fixed in commit f6cd7daecff5 ("drm: Release
> > driver references to handle before making it available again"), but now
> > the exposure is
On Tue, 2017-08-22 at 13:33 +0100, Chris Wilson wrote:
> Quoting Szwichtenberg, Radoslaw (2017-08-22 12:56:00)
> > On Tue, 2017-08-22 at 01:31 +0300, Arkadiusz Hiler wrote:
> > > On Mon, Aug 21, 2017 at 09:39:24PM +0200, Daniel Vetter wrote:
> > > > On Mon, Aug 21, 2017 at 11:21:49AM +0100, Chris W
On 22/08/17 12:59, Chris Wilson wrote:
Quoting Lionel Landwerlin (2017-08-22 12:45:47)
On 08/08/17 15:21, Matthew Auld wrote:
On 4 August 2017 at 12:20, Lionel Landwerlin
wrote:
static void
@@ -1336,6 +1504,66 @@ print_reports(uint32_t *oa_report0, uint32_t
*oa_report1, int fmt)
}
== Series Details ==
Series: pm_rps: Changes in waitboost scenario (rev4)
URL : https://patchwork.freedesktop.org/series/28966/
State : success
== Summary ==
IGT patchset tested on top of latest successful build
4524a8951348a31ae5dabfc4c69f2a835034ec3e tests: Introduce audio tests, starting
w
By using ftw, we avoid the issue of having to handle directory recursion
ourselves and can focus on the test of checking the reading a
sysfs/debugfs does not break runtime suspend. In the process, disregard
errors when opening the individual files as they may fail for other
reasons.
Signed-off-by:
On Tue, 22 Aug 2017, Daniel Vetter wrote:
> On Tue, Aug 22, 2017 at 09:06:36AM +0200, Daniel Vetter wrote:
>> On Mon, Aug 21, 2017 at 01:11:20PM -0700, Rodrigo Vivi wrote:
>> > Soon we will need to extend qf for very specific
>> > usages of our internal maintenance and rebase bot.
>> >
>> > So in
On Tue, Aug 22, 2017 at 09:06:36AM +0200, Daniel Vetter wrote:
> On Mon, Aug 21, 2017 at 01:11:20PM -0700, Rodrigo Vivi wrote:
> > Soon we will need to extend qf for very specific
> > usages of our internal maintenance and rebase bot.
> >
> > So instead of creating yet another config file
> > let'
On Tue, Aug 22, 2017 at 03:08:49PM +0300, Petri Latvala wrote:
> The list has been unmaintained and unused. The set of tests is a
> subset of what CI runs in sharded runs so we are running all of them
> already.
>
> Signed-off-by: Petri Latvala
Acked-by: Arkadiusz Hiler
_
CI is observing sporadical failures in pm_rps subtests.
There are a couple of reasons. One of them is the fact that
on gen6, gen7 and gen7.5, max frequency (as in the HW limit)
is not set to RP0, but the value obtaind from PCODE (which
may be different from RP0). Thus the test is operating under
wr
== Series Details ==
Series: intel-ci: Remove generic.testlist
URL : https://patchwork.freedesktop.org/series/29139/
State : success
== Summary ==
IGT patchset tested on top of latest successful build
4524a8951348a31ae5dabfc4c69f2a835034ec3e tests: Introduce audio tests, starting
with HDMI si
Quoting Szwichtenberg, Radoslaw (2017-08-22 12:56:00)
> On Tue, 2017-08-22 at 01:31 +0300, Arkadiusz Hiler wrote:
> > On Mon, Aug 21, 2017 at 09:39:24PM +0200, Daniel Vetter wrote:
> > > On Mon, Aug 21, 2017 at 11:21:49AM +0100, Chris Wilson wrote:
> > > > Quoting Chris Wilson (2017-08-21 10:53:36)
== Series Details ==
Series: igt: Add gem_close (rev2)
URL : https://patchwork.freedesktop.org/series/29135/
State : success
== Summary ==
IGT patchset tested on top of latest successful build
4524a8951348a31ae5dabfc4c69f2a835034ec3e tests: Introduce audio tests, starting
with HDMI signal int
On Tue, 2017-08-22 at 12:37 +0300, Mika Kuoppala wrote:
> Engine's execlist related items have been increasing to
> a point where a separate struct is warranted. Carve execlist
> specific items to a dedicated struct to add clarity.
>
> Suggested-by: Chris Wilson
> Signed-off-by: Mika Kuoppala
The list has been unmaintained and unused. The set of tests is a
subset of what CI runs in sharded runs so we are running all of them
already.
Signed-off-by: Petri Latvala
---
tests/intel-ci/Makefile.am | 1 -
tests/intel-ci/README | 6 --
tests/intel-ci/generic.testlist | 125
== Series Details ==
Series: series starting with [1/3] drm/i915: Assert the context is not closed
on object-close
URL : https://patchwork.freedesktop.org/series/29137/
State : success
== Summary ==
Series 29137v1 series starting with [1/3] drm/i915: Assert the context is not
closed on objec
Thanks Chris,
With this series the test pin-pointed in the bug now pass.
Tested-by: Marta Lofstedt
> -Original Message-
> From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf
> Of Chris Wilson
> Sent: Tuesday, August 22, 2017 2:05 PM
> To: intel-gfx@lists.freedeskto
Quoting Lionel Landwerlin (2017-08-22 12:45:47)
> On 08/08/17 15:21, Matthew Auld wrote:
> > On 4 August 2017 at 12:20, Lionel Landwerlin
> > wrote:
> >> static void
> >> @@ -1336,6 +1504,66 @@ print_reports(uint32_t *oa_report0, uint32_t
> >> *oa_report1, int fmt)
> >> }
> >>
> >> static v
On Tue, 2017-08-22 at 01:31 +0300, Arkadiusz Hiler wrote:
> On Mon, Aug 21, 2017 at 09:39:24PM +0200, Daniel Vetter wrote:
> > On Mon, Aug 21, 2017 at 11:21:49AM +0100, Chris Wilson wrote:
> > > Quoting Chris Wilson (2017-08-21 10:53:36)
> > > > Quoting Arkadiusz Hiler (2017-08-21 10:42:25)
> > > >
On 08/08/17 15:21, Matthew Auld wrote:
On 4 August 2017 at 12:20, Lionel Landwerlin
wrote:
From: Robert Bragg
Signed-off-by: Robert Bragg
Signed-off-by: Lionel Landwerlin
---
tests/perf.c | 806 ---
1 file changed, 768 insertions(+)
== Series Details ==
Series: drm/i915: Add more latency to avoid display flicker
URL : https://patchwork.freedesktop.org/series/29136/
State : success
== Summary ==
Series 29136v1 drm/i915: Add more latency to avoid display flicker
https://patchwork.freedesktop.org/api/1.0/series/29136/revisio
1 - 100 of 125 matches
Mail list logo