== Series Details ==
Series: drm/i915/jsl: Add W/A 1409054076 for JSL (rev3)
URL : https://patchwork.freedesktop.org/series/90129/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10102_full -> Patchwork_20155_full
Summary
---
Chrome platforms is unable to handle reading from -1.
It terminates the test after reporting buffer overflow.
Hence, changed the address for invalid buffer to NULL instead of -1.
With this change, errno becomes EINTR when reading from NULL
location. To accomodate, also changing the check of errno t
Without wait for vblank, CRC mismatch is seen
between big and small CRC on few systems
Change-Id: I3bec931aa901130997e693ac1cacf389e2a8100f
Signed-off-by: Vidya Srinivas
---
tests/kms_big_fb.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/tests/kms_big_fb.c b/tests/km
On Thu, May 6, 2021 at 5:46 PM Rafael J. Wysocki wrote:
>
> On Tue, May 4, 2021 at 10:08 AM Chris Chiu wrote:
> >
> > Hi,
> > We have some Intel laptops (11th generation CPU) with NVIDIA GPU
> > suffering the same GPU falling off the bus problem while exiting
> > s2idle with external display
| ^~~~
drivers/gpu/drm/i915/i915_reg.h:185:47: note: in definition of macro '_MMIO'
185 | #define _MMIO(r) ((const i915_reg_t){ .reg = (r) })
| ^
Caused by commit
0633cdcbaa77 ("drm/i915/d
Hi all,
On Thu, 20 May 2021 10:19:10 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the drm-intel tree got a conflict in:
>
> drivers/gpu/drm/i915/i915_mm.c
>
> between commit:
>
> 293837b9ac8d ("Revert "i915: fix remap_io_sg to verify the pgprot"")
>
> from Linus' tree an
Hi all,
Today's linux-next merge of the amdgpu tree got a conflict in:
drivers/gpu/drm/amd/amdkfd/kfd_device.c
between commit:
e9669fb78262 ("drm/amdgpu: Add early fini callback")
from the drm-misc tree and commit:
814ab9930cfd ("drm/amdkfd: register HMM device private zone")
from the
Hi all,
Today's linux-next merge of the amdgpu tree got a conflict in:
drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c
between commit:
35bba8313b95 ("drm/amdgpu: Convert driver sysfs attributes to static
attributes")
from the drm-misc tree and commit:
589939d40116 ("drm/amdgpu: fix coding
== Series Details ==
Series: drm/i915/display: fix typo when returning table
URL : https://patchwork.freedesktop.org/series/90385/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10116 -> Patchwork_20166
Summary
---
**
Hi all,
Today's linux-next merge of the amdgpu tree got a conflict in:
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
between commit:
f89f8c6bafd0 ("drm/amdgpu: Guard against write accesses after device removal")
from the drm-misc tree and commit:
0ccc3ccf5b3a ("drm/amdgpu: re-apply "use the ne
Hi all,
Today's linux-next merge of the amdgpu tree got a conflict in:
drivers/gpu/drm/amd/amdgpu/amdgpu_gtt_mgr.c
between commit:
35bba8313b95 ("drm/amdgpu: Convert driver sysfs attributes to static
attributes")
from the drm-misc tree and commit:
a614b336f1c1 ("drm/amdgpu: fix coding
== Series Details ==
Series: series starting with [1/2] drm/i915/cmdparser: No-op failed batches on
all platforms (rev2)
URL : https://patchwork.freedesktop.org/series/90310/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10102_full -> Patchwork_20154_full
== Series Details ==
Series: drm/i915/display: fix typo when returning table
URL : https://patchwork.freedesktop.org/series/90385/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
88e8d46ff078 drm/i915/display: fix typo when returning table
-:9: WARNING:COMMIT_LOG_LONG_LINE: Possi
== Series Details ==
Series: More DMC cleanup (rev2)
URL : https://patchwork.freedesktop.org/series/90379/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10116 -> Patchwork_20165
Summary
---
**SUCCESS**
No regressi
Fix table returned when port_clock > 27:
drivers/gpu/drm/i915/display/intel_ddi_buf_trans.c:752:47: error:
variable 'adlp_dkl_phy_dp_ddi_trans_hbr2_hbr3' is not needed and will not be
emitted [-Werror,-Wunneeded-internal-declaration]
static const struct tgl_dkl_phy_ddi_buf_tr
== Series Details ==
Series: More DMC cleanup (rev2)
URL : https://patchwork.freedesktop.org/series/90379/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
06268e3a934f drm/i915/dmc: s/DRM_ERROR/drm_err
-:79: WARNING:OOM_MESSAGE: Possible unnecessary 'out of memory' message
#79: F
Move struct intel_dmc from i915_drv.h to intel_dmc.h.
Signed-off-by: Anusha Srivatsa
---
drivers/gpu/drm/i915/display/intel_dmc.h | 17 +
drivers/gpu/drm/i915/i915_drv.h | 18 +-
2 files changed, 18 insertions(+), 17 deletions(-)
diff --git a/drivers/gpu
Use new format of debug messages across intel_csr.
While at it, change some function definitions which now
need dev_priv for drm_err and drm_info etc.
v2: use container_of() (Jani)
Cc: Jani Nikula
Suggested-by: Lucas De Marchi
Signed-off-by: Anusha Srivatsa
Reviewed-by: Lucas De Marchi
---
We check for dmc_payload being there at various points in the driver.
Replace it with the helper.
v2: rebased.
v3: Move intel_dmc to intel_dmc.h in another patch (Lucas)
Cc: Lucas De Marchi
Signed-off-by: Anusha Srivatsa
Reviewed-by: Lucas De Marchi
---
.../gpu/drm/i915/display/intel_display_
Last of prep patches before Pipe DMC patches
can land.
v2: Add struct intel_dmc to intel_dmc.h in a separate
patch
Anusha Srivatsa (3):
drm/i915/dmc: s/DRM_ERROR/drm_err
drm/i915/dmc: Add intel_dmc_has_payload() helper
drm/i915/dmc: Move struct intel_dmc to intel_dmc.h
.../drm/i915/displa
On Thu, May 20, 2021 at 10:46 AM Matthew Brost wrote:
>
> On Thu, May 20, 2021 at 01:11:59PM +0200, Christian König wrote:
> > Am 19.05.21 um 18:51 schrieb Matthew Brost:
> > > On Wed, May 19, 2021 at 01:45:39PM +0200, Christian König wrote:
> > > > Oh, yeah we call that gang submit on the AMD sid
On Wed, 19 May 2021 10:15:35 +0200, Mauro Carvalho Chehab wrote:
> There are some places at drm that ended receiving a
> REPLACEMENT CHARACTER U+fffd ('�'), probably because of
> some bad charset conversion.
>
> Fix them by using what it seems to be the proper
> character.
Applied to
ht
On Thu, May 20, 2021 at 11:36:08AM -0700, Anusha Srivatsa wrote:
We check for dmc_payload being there at various points in the driver.
Replace it with the helper.
v2: rebased.
Cc: Lucas De Marchi
Signed-off-by: Anusha Srivatsa
---
.../drm/i915/display/intel_display_debugfs.c | 4 ++--
.../dr
On Thu, May 20, 2021 at 11:36:07AM -0700, Anusha Srivatsa wrote:
Use new format of debug messages across intel_csr.
While at it, change some function definitions which now
need dev_priv for drm_err and drm_info etc.
v2: use container_of() (Jani)
Cc: Jani Nikula
Suggested-by: Lucas De Marchi
On Thu, May 20, 2021 at 08:10:59AM -0700, Matthew Brost wrote:
> On Thu, May 20, 2021 at 11:54:25AM +0200, Daniel Vetter wrote:
> > On Wed, May 19, 2021 at 7:19 PM Matthew Brost
> > wrote:
> > >
> > > On Wed, May 19, 2021 at 01:10:04PM +0200, Daniel Vetter wrote:
> > > > On Tue, May 18, 2021 at 0
On Thu, May 20, 2021 at 11:57:44AM +0100, Tvrtko Ursulin wrote:
>
> On 20/05/2021 10:54, Daniel Vetter wrote:
> > On Wed, May 19, 2021 at 7:19 PM Matthew Brost
> > wrote:
> > >
> > > On Wed, May 19, 2021 at 01:10:04PM +0200, Daniel Vetter wrote:
> > > > On Tue, May 18, 2021 at 04:58:30PM -0700,
== Series Details ==
Series: More DMC cleanup
URL : https://patchwork.freedesktop.org/series/90379/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10113 -> Patchwork_20164
Summary
---
**SUCCESS**
No regressions fou
== Series Details ==
Series: More DMC cleanup
URL : https://patchwork.freedesktop.org/series/90379/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
a52e01980968 drm/i915/dmc: s/DRM_ERROR/drm_err
-:36: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#36: FILE:
== Series Details ==
Series: drm/dp_mst: Use kHz as link rate units when settig source max link caps
at init (rev2)
URL : https://patchwork.freedesktop.org/series/90099/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10113 -> Patchwork_20163
===
We check for dmc_payload being there at various points in the driver.
Replace it with the helper.
v2: rebased.
Cc: Lucas De Marchi
Signed-off-by: Anusha Srivatsa
---
.../drm/i915/display/intel_display_debugfs.c | 4 ++--
.../drm/i915/display/intel_display_power.c| 16 +++---
driv
Use new format of debug messages across intel_csr.
While at it, change some function definitions which now
need dev_priv for drm_err and drm_info etc.
v2: use container_of() (Jani)
Cc: Jani Nikula
Suggested-by: Lucas De Marchi
Signed-off-by: Anusha Srivatsa
---
drivers/gpu/drm/i915/display/i
Last of prep patches before Pipe DMC patches
can land.
Anusha Srivatsa (2):
drm/i915/dmc: s/DRM_ERROR/drm_err
drm/i915/dmc: Add intel_dmc_has_payload() helper
.../drm/i915/display/intel_display_debugfs.c | 4 +-
.../drm/i915/display/intel_display_power.c| 16 +++---
drivers/gpu/drm/i91
== Series Details ==
Series: drm/dp_mst: Use kHz as link rate units when settig source max link caps
at init (rev2)
URL : https://patchwork.freedesktop.org/series/90099/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
2bc1c0fbd55e drm/dp_mst: Use kHz as link rate units when sett
On Thu, May 20, 2021 at 6:31 PM Christian König
wrote:
>
> Yeah, having the timestamp is a good idea as well.
>
> drm-driver: i915
>
> I think we should rather add something like printing
> file_operations->owner->name to the common fdinfo code.
>
> This way we would have something common for a
On Thu, May 06, 2021 at 12:13:18PM -0700, Matthew Brost wrote:
> From: Daniele Ceraolo Spurio
>
> If we're about to sanitize the GuC, something might have going wrong
> beforehand, so we should avoid trying to talk to it. Even if GuC is
> still running fine, the sanitize will reset its internal s
Yeah, having the timestamp is a good idea as well.
drm-driver: i915
I think we should rather add something like printing
file_operations->owner->name to the common fdinfo code.
This way we would have something common for all drivers in the system.
I'm just not sure if that also works if th
== Series Details ==
Series: Per client engine busyness
URL : https://patchwork.freedesktop.org/series/90375/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10113 -> Patchwork_20162
Summary
---
**SUCCESS**
No regre
== Series Details ==
Series: Per client engine busyness
URL : https://patchwork.freedesktop.org/series/90375/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
-
+drivers/gpu/drm/i915/display/intel_d
== Series Details ==
Series: Per client engine busyness
URL : https://patchwork.freedesktop.org/series/90375/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
1455dee675ac drm/i915: Explicitly track DRM clients
-:84: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does
== Series Details ==
Series: Core TTM changes for i915 TTM enabling
URL : https://patchwork.freedesktop.org/series/90373/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10113 -> Patchwork_20161
Summary
---
**SUCCESS**
On Thu, May 20, 2021 at 01:11:59PM +0200, Christian König wrote:
> Am 19.05.21 um 18:51 schrieb Matthew Brost:
> > On Wed, May 19, 2021 at 01:45:39PM +0200, Christian König wrote:
> > > Oh, yeah we call that gang submit on the AMD side.
> > >
> > > Had already some internal discussions how to impl
== Series Details ==
Series: Core TTM changes for i915 TTM enabling
URL : https://patchwork.freedesktop.org/series/90373/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
+./drivers/gpu/drm/amd/amdg
== Series Details ==
Series: Core TTM changes for i915 TTM enabling
URL : https://patchwork.freedesktop.org/series/90373/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
6eeb4e1f8ab7 drm/ttm: Add a generic TTM memcpy move for page-based iomem
-:70: CHECK:ARCH_DEFINES: architectur
On Thu, May 20, 2021 at 11:54:25AM +0200, Daniel Vetter wrote:
> On Wed, May 19, 2021 at 7:19 PM Matthew Brost wrote:
> >
> > On Wed, May 19, 2021 at 01:10:04PM +0200, Daniel Vetter wrote:
> > > On Tue, May 18, 2021 at 04:58:30PM -0700, Matthew Brost wrote:
> > > > Add entry fpr i915 new parallel
On Thu, 2021-05-20 at 17:09 +0200, Thomas Hellström wrote:
>
> +EXPORT_SYMBOL(ttm_tt_unpopulate);
Oh, this one was a leftover. It's not meant to be included anymore.
/Thomas
>
> #ifdef CONFIG_DEBUG_FS
>
___
Intel-gfx mailing list
Intel-gfx@lis
From: Tvrtko Ursulin
Continuing on the identically named thread. First six patches are i915 specific
so please mostly look at the last one only which discusses the common options
for DRM drivers.
I haven't updated intel_gpu_top to use this yet so can't report any performance
numbers.
Tvrtko Urs
From: Tvrtko Ursulin
Similar to AMD commit
874442541133 ("drm/amdgpu: Add show_fdinfo() interface"), using the
infrastructure added in previous patches, we add basic client info
and GPU engine utilisation for i915.
Example of the output:
pos:0
flags: 012
mnt_id: 21
drm-driver:
From: Tvrtko Ursulin
Track context active (on hardware) status together with the start
timestamp.
This will be used to provide better granularity of context
runtime reporting in conjunction with already tracked pphwsp accumulated
runtime.
The latter is only updated on context save so does not g
From: Tvrtko Ursulin
We soon want to start answering questions like how much GPU time is the
context belonging to a client which exited still using.
To enable this we start tracking all context belonging to a client on a
separate list.
Signed-off-by: Tvrtko Ursulin
Reviewed-by: Aravind Iddamse
From: Tvrtko Ursulin
If we make GEM contexts keep a reference to i915_drm_client for the whole
of their lifetime, we can consolidate the current task pid and name usage
by getting it from the client.
v2: Don't bother supporting selftests contexts from debugfs. (Chris)
v3 (Lucas): Finish construc
From: Tvrtko Ursulin
Some clients have the DRM fd passed to them over a socket by the X server.
Grab the real client and pid when they create their first context and
update the exposed data for more useful enumeration.
To enable lockless access to client name and pid data from the following
pat
On Mon, May 10, 2021 at 05:25:25PM +0200, Christoph Hellwig wrote:
> Hi all,
>
> swiotlb_max_segment is a rather strange "API" export by swiotlb.c,
> and i915 is the only (remaining) user.
>
> swiotlb_max_segment returns 0 if swiotlb is not in use, 1 if
> SWIOTLB_FORCE is set or swiotlb-zen is se
From: Tvrtko Ursulin
As contexts are abandoned we want to remember how much GPU time they used
(per class) so later we can used it for smarter purposes.
As GEM contexts are closed we want to have the DRM client remember how
much GPU time they used (per class) so later we can used it for smarter
From: Tvrtko Ursulin
Tracking DRM clients more explicitly will allow later patches to
accumulate past and current GPU usage in a centralised place and also
consolidate access to owning task pid/name.
Unique client id is also assigned for the purpose of distinguishing/
consolidating between multi
If the bo is idle when calling ttm_bo_pipeline_gutting(), we unnecessarily
create a ghost object and push it out to delayed destroy.
Fix this by adding a path for idle, and document the function.
Also avoid having the bo end up in a bad state vulnerable to user-space
triggered kernel BUGs if the c
We are calling the eviction_valuable driver callback at eviction time to
determine whether we actually can evict a buffer object.
The upcoming i915 TTM backend needs the same functionality for swapout,
and that might actually be beneficial to other drivers as well.
Add an eviction_valuable call al
This is mainly a pre-check that the core TTM changes for the initial
i915 TTM patch series look reasonably ok.
Main thing is we add the new page-based iomem memcpy util to TTM, and
for some speed the copy-from-wc-x86-only prefetching memcpy to core drm.
Note that the legacy memcpy path is largely
Use fast wc memcpy for reading out of wc memory for TTM bo moves.
Cc: Dave Airlie
Cc: Christian König
Cc: Daniel Vetter
Signed-off-by: Thomas Hellström
---
drivers/gpu/drm/ttm/ttm_bo_util.c | 18 +-
1 file changed, 17 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/
Memcpy from wc will be used as well by TTM memcpy.
Move it to core drm, and make the interface do the right thing
even on !X86.
Cc: Christian König
Cc: Daniel Vetter
Cc: Dave Airlie
Signed-off-by: Thomas Hellström
---
drivers/gpu/drm/Makefile | 2 +-
drivers/gpu/drm/drm_
The internal ttm_bo_util memcpy uses ioremap functionality, and while it
probably might be possible to use it for copying in- and out of
sglist represented io memory, using io_mem_reserve() / io_mem_free()
callbacks, that would cause problems with fault().
Instead, implement a method mapping page-b
On Thu, May 20, 2021 at 08:35:14AM +0100, Matthew Auld wrote:
> From: Chris Wilson
>
> The first tracepoint for a request is trace_dma_fence_init called before
> we have associated the request with a device. The tracepoint uses
> fence->ops->get_driver_name() as a pretty name, and as we try to re
Am 20.05.21 um 16:11 schrieb Daniel Vetter:
On Wed, May 19, 2021 at 11:17:24PM +, Nieto, David M wrote:
[AMD Official Use Only]
Parsing over 550 processes for fdinfo is taking between 40-100ms single
threaded in a 2GHz skylake IBRS within a VM using simple string
comparisons and DIRent p
On Wed, May 19, 2021 at 11:17:24PM +, Nieto, David M wrote:
> [AMD Official Use Only]
>
> Parsing over 550 processes for fdinfo is taking between 40-100ms single
> threaded in a 2GHz skylake IBRS within a VM using simple string
> comparisons and DIRent parsing. And that is pretty much the wors
Hi Dave, Daniel,
Here's this week fix for drm-misc-fixes
Maxime
drm-misc-fixes-2021-05-20:
Just a single fix for a dma-buf related WARN
The following changes since commit c55b44c9386f3ee1b08752638559f19deaf6040d:
Merge drm/drm-fixes into drm-misc-fixes (2021-05-11 13:35:52 +0200)
are availab
On Thu, 20 May 2021 at 09:23, samirweng1979 wrote:
>
> From: wengjianfeng
>
> change 'freqency' to 'frequency'.
>
> Signed-off-by: wengjianfeng
Pushed to intel-gt-next. Thanks.
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.f
== Series Details ==
Series: drm/i915/gt: fix typo issue
URL : https://patchwork.freedesktop.org/series/90364/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10112 -> Patchwork_20160
Summary
---
**SUCCESS**
No regr
On Thu, Apr 29, 2021 at 12:28 AM Hsin-Yi Wang wrote:
>
> drm_dev_register() sets connector->registration_state to
> DRM_CONNECTOR_REGISTERED and dev->registered to true. If
> drm_connector_set_panel_orientation() is first called after
> drm_dev_register(), it will fail several checks and results i
== Series Details ==
Series: drm/i915: Implement PSF GV point support
URL : https://patchwork.freedesktop.org/series/90361/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10111 -> Patchwork_20159
Summary
---
**FAILURE
From: wengjianfeng
change 'freqency' to 'frequency'.
Signed-off-by: wengjianfeng
---
drivers/gpu/drm/i915/gt/selftest_rps.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/gt/selftest_rps.c
b/drivers/gpu/drm/i915/gt/selftest_rps.c
index 967641f..71
Hello everyone!
The X.org board is soliciting proposals to host XDC in 2022. Since
XDC 2021 is being held in Europe this year (although virtually), we've
decided to host in North America. However, the board is open to other
locations, especially if there's an interesting co-location with
another c
[AMD Official Use Only]
Parsing over 550 processes for fdinfo is taking between 40-100ms single
threaded in a 2GHz skylake IBRS within a VM using simple string comparisons and
DIRent parsing. And that is pretty much the worst case scenario with some more
optimized implementations.
David
__
Hi Dave & Daniel -
drm-intel-fixes-2021-05-20:
drm/i915 fixes for v5.13-rc3:
- Pin the L-shape quirked object as unshrinkable to fix crashes
- Disable HiZ Raw Stall Optimization on broken gen7 to fix glitches, gfx
corruption
- GVT: Move mdev attribute groups into kvmgt module to fix kconfig dep
== Series Details ==
Series: drm/i915: Implement PSF GV point support
URL : https://patchwork.freedesktop.org/series/90361/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
3c2cdfef9cf5 drm/i915: Implement PSF GV point support
-:50: CHECK:PARENTHESIS_ALIGNMENT: Alignment should ma
PSF GV points are an additional factor that can limit the
bandwidth available to display, separate from the traditional
QGV points. Whereas traditional QGV points represent possible
memory clock frequencies, PSF GV points reflect possible
frequencies of the memory fabric.
Switching between PSF GV
Am 19.05.21 um 18:51 schrieb Matthew Brost:
On Wed, May 19, 2021 at 01:45:39PM +0200, Christian König wrote:
Oh, yeah we call that gang submit on the AMD side.
Had already some internal discussions how to implement this, but so far
couldn't figure out how to cleanly introduce that into the DRM
On 20/05/2021 10:54, Daniel Vetter wrote:
On Wed, May 19, 2021 at 7:19 PM Matthew Brost wrote:
On Wed, May 19, 2021 at 01:10:04PM +0200, Daniel Vetter wrote:
On Tue, May 18, 2021 at 04:58:30PM -0700, Matthew Brost wrote:
Add entry fpr i915 new parallel submission uAPI plan.
v2:
(Daniel
== Series Details ==
Series: ADL-P: more reviewed patches (rev2)
URL : https://patchwork.freedesktop.org/series/90305/
State : failure
== Summary ==
Applying: drm/i915/xelpd: Calculate VDSC RC parameters
Using index info to reconstruct a base tree...
M drivers/gpu/drm/i915/display/intel_
Hello!
Registration & Call for Proposals are now open for XDC 2021, which will
take place on September 15-17, 2021. This year we will repeat as
virtual event.
https://indico.freedesktop.org/event/1/
As usual, the conference is free of charge and open to the general
public. If you plan on attendi
On Wed, May 19, 2021 at 7:19 PM Matthew Brost wrote:
>
> On Wed, May 19, 2021 at 01:10:04PM +0200, Daniel Vetter wrote:
> > On Tue, May 18, 2021 at 04:58:30PM -0700, Matthew Brost wrote:
> > > Add entry fpr i915 new parallel submission uAPI plan.
> > >
> > > v2:
> > > (Daniel Vetter):
> > > - E
== Series Details ==
Series: drm/i915: Use DRIVER_NAME for tracing unattached requests
URL : https://patchwork.freedesktop.org/series/90351/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10110 -> Patchwork_20157
Summary
---
On 19/05/2021 19:23, Daniel Vetter wrote:
On Wed, May 19, 2021 at 6:16 PM Tvrtko Ursulin
wrote:
On 18/05/2021 10:40, Tvrtko Ursulin wrote:
On 18/05/2021 10:16, Daniel Stone wrote:
Hi,
On Tue, 18 May 2021 at 10:09, Tvrtko Ursulin
wrote:
I was just wondering if stat(2) and a chrdev majo
On Wed, 19 May 2021 16:49:35 +0300
Ville Syrjälä wrote:
> On Wed, May 19, 2021 at 12:34:05PM +0300, Pekka Paalanen wrote:
> > On Wed, 12 May 2021 16:04:16 +0300
> > Ville Syrjälä wrote:
> >
> > > On Wed, May 12, 2021 at 02:06:56PM +0200, Werner Sembach wrote:
> > > > Hello,
> > > >
> > > >
== Series Details ==
Series: drm/i915: Invoke another _DSM to enable MUX on HP Workstation laptops
(rev2)
URL : https://patchwork.freedesktop.org/series/89503/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10109 -> Patchwork_20156
=
From: Chris Wilson
The first tracepoint for a request is trace_dma_fence_init called before
we have associated the request with a device. The tracepoint uses
fence->ops->get_driver_name() as a pretty name, and as we try to report
the device name this oopses as it is then NULL. Support the early
t
== Series Details ==
Series: drm/i915: Invoke another _DSM to enable MUX on HP Workstation laptops
(rev2)
URL : https://patchwork.freedesktop.org/series/89503/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
dcae1309b1dc drm/i915: Invoke another _DSM to enable MUX on HP Workstat
85 matches
Mail list logo
