For topic/intel-for-CI branch only.
We have established previously we stop using relocations starting
from gen12 platforms with Tigerlake as an exception. We keep this
statement but we want to enable relocations conditionally for
Alderlake S+P under require_force_probe flag set.
Keeping
== Series Details ==
Series: Explicity steer l3bank multicast reads when necessary (rev5)
URL : https://patchwork.freedesktop.org/series/91485/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10233 -> Patchwork_20394
Summary
Hi all,
Today's linux-next merge of the drm tree got a conflict in:
drivers/gpu/drm/vc4/vc4_hdmi.c
between commit:
9984d6664ce9 ("drm/vc4: hdmi: Make sure the controller is powered in detect")
from the drm-misc-fixes tree and commit:
6800234ceee0 ("drm/vc4: hdmi: Convert to gpiod")
On 6/15/2021 5:13 PM, Matthew Brost wrote:
From: Michal Wajdeczko
Most of the changes to the 62.0.0 firmware revolved around CTB
communication channel. Conform to the new (stable) CTB protocol.
v2:
(Michal)
Add values back to kernel DOC for actions
(Docs)
Add 'CT buffer' back in
On 6/15/2021 3:43 PM, Matthew Brost wrote:
The submission tasklet operates on i915_sched_engine, thus it is the
correct place for it.
v3:
(Jason Ekstrand)
Change sched_engine->engine to a void* private data pointer
Add kernel doc
v4:
(Daniele)
Update private_data comment
Set
== Series Details ==
Series: Explicity steer l3bank multicast reads when necessary (rev5)
URL : https://patchwork.freedesktop.org/series/91485/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
311242e9e0f0 drm/i915: extract steered reg access to common function
-:90:
Because Render Power Gating restricts us to just a single subslice as a
valid steering target for reads of multicast registers in a SUBSLICE
range, the default steering we setup at init may not lead to a suitable
target for L3BANK multicast register. In cases where it does not, use
explicit
== Series Details ==
Series: series starting with [1/6] drm/i915/display/psr: Handle SU Y granularity
URL : https://patchwork.freedesktop.org/series/91594/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10233_full -> Patchwork_20393_full
== Series Details ==
Series: Explicity steer l3bank multicast reads when necessary (rev4)
URL : https://patchwork.freedesktop.org/series/91485/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10230_full -> Patchwork_20391_full
== Series Details ==
Series: drm/i915: return DRIVER_NAME for the fence driver name
URL : https://patchwork.freedesktop.org/series/91573/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10230_full -> Patchwork_20388_full
== Series Details ==
Series: drm/i915/gt: Fix duplicate included intel_region_lmem.h
URL : https://patchwork.freedesktop.org/series/91571/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10230_full -> Patchwork_20387_full
== Series Details ==
Series: series starting with [1/6] drm/i915/display/psr: Handle SU Y granularity
URL : https://patchwork.freedesktop.org/series/91594/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10233 -> Patchwork_20393
== Series Details ==
Series: series starting with [1/6] drm/i915/display/psr: Handle SU Y granularity
URL : https://patchwork.freedesktop.org/series/91594/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
47efae2a069f drm/i915/display/psr: Handle SU Y granularity
a03bc073ba13
== Series Details ==
Series: drm/dp_mst: Add missing drm parameters to recently added call to
drm_dbg_kms()
URL : https://patchwork.freedesktop.org/series/91592/
State : failure
== Summary ==
Applying: drm/dp_mst: Add missing drm parameters to recently added call to
drm_dbg_kms()
Using
In some modes there is not enough time during hblank to transmit PSR2
SDP plus the pixels CRC SDP, if such case happens PSR2 needs to be
disabled.
But eDP spec 1.4b allows to transmit PSR2 SDP in a prior scanline
alone and than later the CRC SDP, allowing PSR2 to be enabled in
those hblank
Implements changes around PSR for alderlake-P:
- EDP_SU_TRACK_ENABLE was removed and bit 30 now has other function
- Some bits of PSR2_MAN_TRK_CTL moved and SF_PARTIAL_FRAME_UPDATE was
removed setting SU_REGION_START/END_ADDR will do this job
- SU_REGION_START/END_ADDR have now line granularity
PSR2 is not compatible with DC3CO or VRR in this stepping, so not
enabling PSR2 if VRR will be enabled or not enabling DC3CO if PSR2 is
possible.
BSpec: 54369
Cc: Gwan-gyeong Mun
Cc: Matt Atwood
Signed-off-by: José Roberto de Souza
---
drivers/gpu/drm/i915/display/intel_psr.c | 12
We were only handling X and width granularity, what was causing issues
when sink had a granularity different than 4.
While at it, renaming su_x_granularity to su_w_granularity to better
match reality.
Cc: Gwan-gyeong Mun
Signed-off-by: José Roberto de Souza
---
Another WA that is required for PSR2.
BSpec: 54369
Cc: Gwan-gyeong Mun
Cc: Matt Atwood
Signed-off-by: José Roberto de Souza
---
drivers/gpu/drm/i915/display/intel_psr.c | 15 +++
drivers/gpu/drm/i915/i915_reg.h | 8
2 files changed, 23 insertions(+)
diff --git
The PSR2_CTL io buffer wake and fast wake values do not match
expected in pre production hardware, so here adding a table that
matches with HW to program it with values that HW expect.
Cc: Gwan-gyeong Mun
Signed-off-by: José Roberto de Souza
---
drivers/gpu/drm/i915/display/intel_psr.c | 29
-static int mtty_reset(struct mdev_device *mdev)
+static int mtty_reset(struct mdev_state *mdev_stte)
Nit pick:
s/mdev_stte/mdev_state
+static const struct vfio_device_ops mtty_dev_ops = {
+ .name = "vfio-mdev",
I think name should be different that 'vfio-mdev', probably
On 6/15/2021 7:05 PM, Christoph Hellwig wrote:
From: Jason Gunthorpe
This allows a mdev driver to opt out of using vfio_mdev.c, instead the
driver will provide a 'struct mdev_driver' and register directly with the
driver core.
Much of mdev_parent_ops becomes unused in this mode:
-
On 6/15/2021 7:05 PM, Christoph Hellwig wrote:
From: Jason Gunthorpe
For some reason the vfio_mdev shim mdev_driver has its own module and
kconfig. As the next patch requires access to it from mdev.ko merge the
two modules together and remove VFIO_MDEV_DEVICE.
A later patch deletes this
On 6/15/2021 7:05 PM, Christoph Hellwig wrote:
really_probe tries to special case errors from ->probe, but due to all
other initialization added to the function over time now a lot of
internal errors hit that code path as well. Untangle that by adding
a new probe_err local variable and apply
Hi Jason,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-tip/drm-tip drm-exynos/exynos-drm-next
next-20210616]
[cannot apply to tegra-drm/drm/tegra/for-next drm/drm-next v5.13-rc6]
[If your patch
== Series Details ==
Series: Explicity steer l3bank multicast reads when necessary (rev4)
URL : https://patchwork.freedesktop.org/series/91485/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10230 -> Patchwork_20391
Summary
Re-reported.
-Original Message-
From: Deak, Imre
Sent: Wednesday, June 16, 2021 9:20 AM
To: intel-gfx@lists.freedesktop.org; Chris Chiu ;
Shankar, Uma ; Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: Force a TypeC PHY disconnect
during suspend/shutdown
On
Reviewed-by: Lyude Paul
Will go ahead and push this to drm-misc-next-fixes, thanks
On Wed, 2021-06-16 at 12:44 -0700, José Roberto de Souza wrote:
> Commit 3769e4c0af5b ("drm/dp_mst: Avoid to mess up payload table by
> ports in stale topology") added to calls to drm_dbg_kms() but it
> missed
Commit 3769e4c0af5b ("drm/dp_mst: Avoid to mess up payload table by
ports in stale topology") added to calls to drm_dbg_kms() but it
missed the first parameter, the drm device breaking the build.
Fixes: 3769e4c0af5b ("drm/dp_mst: Avoid to mess up payload table by ports in
stale topology")
Cc:
== Series Details ==
Series: Explicity steer l3bank multicast reads when necessary (rev4)
URL : https://patchwork.freedesktop.org/series/91485/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
4c22a61b7efa drm/i915: extract steered reg access to common function
-:90:
== Series Details ==
Series: series starting with [v5,1/7] drm/i915/ttm: add ttm_buddy_man
URL : https://patchwork.freedesktop.org/series/91589/
State : failure
== Summary ==
Applying: drm/i915/ttm: add ttm_buddy_man
.git/rebase-apply/patch:845: new blank line at EOF.
+
warning: 1 line adds
== Series Details ==
Series: drm/i915/ttm: Calculate the object placement at get_pages time (rev2)
URL : https://patchwork.freedesktop.org/series/91586/
State : failure
== Summary ==
Applying: drm/i915/ttm: Calculate the object placement at get_pages time
Using index info to reconstruct a
== Series Details ==
Series: drm/i915: return DRIVER_NAME for the fence driver name
URL : https://patchwork.freedesktop.org/series/91573/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10230 -> Patchwork_20388
Summary
== Series Details ==
Series: drm/i915/gt: Fix duplicate included intel_region_lmem.h
URL : https://patchwork.freedesktop.org/series/91571/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10230 -> Patchwork_20387
Summary
Hi Dave and Daniel,
here's this week's PR for drm-misc-next-fixes.
Best regards
Thomas
drm-misc-next-fixes-2021-06-16:
Short summary of fixes pull:
* hyperv: advertise the correct formatmodifiers for its primary plane
* dp_mst: VCPI fixes to make it work with StarTech hub
The following
Hi Jason,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-tip/drm-tip drm-exynos/exynos-drm-next
tegra-drm/drm/tegra/for-next linus/master v5.13-rc6 next-20210616]
[cannot apply to drm/drm-next
Although most of our multicast registers are replicated per-subslice, we
also have a small number of multicast registers that are replicated
per-l3 bank instead. For both types of multicast registers we need to
make sure we steer reads of these registers to a valid instance.
Ideally we'd like to
== Series Details ==
Series: drm/i915: Force a TypeC PHY disconnect during suspend/shutdown
URL : https://patchwork.freedesktop.org/series/91345/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10205_full -> Patchwork_20334_full
On Wed, Jun 16, 2021 at 10:24:48AM -0400, Rodrigo Vivi wrote:
> On Tue, Jun 15, 2021 at 05:42:12PM -0700, Matt Roper wrote:
> > Although most of our multicast registers are replicated per-subslice, we
> > also have a small number of multicast registers that are replicated
> > per-l3 bank instead.
On Thu, Jun 10, 2021 at 09:28:31PM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Force a TypeC PHY disconnect during suspend/shutdown
> URL : https://patchwork.freedesktop.org/series/91345/
> State : failure
Thanks for the report, testing and review. Pushed to
== Series Details ==
Series: drm/i915/gem: Remove duplicated call to ops->pread
URL : https://patchwork.freedesktop.org/series/91561/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10226_full -> Patchwork_20383_full
Summary
to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Jason-Ekstrand/drm-i915-gem-ioctl-clean-ups-v6/20210616-151016
base: git
Currently we just ignore the I915_BO_ALLOC_CONTIGUOUS flag, which is
fine since everything is already contiguous with the ttm range manager.
However in the next patch we want to switch over to the ttm buddy
manager, where allocations are by default not contiguous.
v2(Thomas):
- Forward
Move back to the buddy allocator for managing device local memory, and
restore the lost mock selftests. Keep around the range manager related
bits, since we likely need this for managing stolen at some point. For
stolen we also don't need to reserve anything so no need to support a
generic reserve
We now have bo->page_alignment which perfectly describes what we need if
we have min page size restrictions for lmem. We can also drop the flag
here, since this is the default behaviour for all objects.
v2(Thomas):
- bo->page_alignment is in page units
Signed-off-by: Matthew Auld
Cc: Thomas
From: Thomas Hellström
Instead of relying on a static placement, calculate at get_pages() time.
This should work for LMEM regions and system for now. For stolen we need
to take preallocated range into account. That will if needed be added
later.
Signed-off-by: Thomas Hellström
Reviewed-by:
We need to be able to build an sg table from our list of buddy blocks,
so that we can later plug this into our ttm backend, and replace our use
of the range manager.
Signed-off-by: Matthew Auld
Cc: Thomas Hellström
Reviewed-by: Thomas Hellström
---
drivers/gpu/drm/i915/i915_scatterlist.c | 80
Now that ttm_resource_manager just returns a generic ttm_resource we
don't need to reference the mm_node stuff anymore which mostly only
makes sense for drm_mm_node. In the next few patches we want switch over
to the ttm_buddy_man which is just another type of ttm_resource so
reflect that in the
Add back our standalone i915_buddy allocator and integrate it into a
ttm_resource_manager. This will plug into our ttm backend for managing
device local-memory in the next couple of patches.
v2(Thomas):
- Return -ENOSPC from the buddy; ttm expects this in order to
trigger eviction
-
Instead of relying on a static placement, calculate at get_pages() time.
This should work for LMEM regions and system for now. For stolen we need
to take preallocated range into account. That will if needed be added
later.
Signed-off-by: Thomas Hellström
Reviewed-by: Matthew Auld
---
v2:
-
Hi
Is there a place where we can download these new firmware images?
Cheers
Mike
On Wed, 16 Jun 2021 at 00:55, Matthew Brost wrote:
> As part of enabling GuC submission [1] we need to update to the latest
> and greatest firmware. This series does that. All backwards
> compatibility breaking
Instead of relying on a static placement, calculate at get_pages() time.
This should work for LMEM regions and system for now. For stolen we need
to take preallocated range into account. That will if needed be added
later.
Signed-off-by: Thomas Hellström
Reviewed-by: Matthew Auld
---
v2:
-
We now have bo->page_alignment which perfectly describes what we need if
we have min page size restrictions for lmem. We can also drop the flag
here, since this is the default behaviour for all objects.
v2(Thomas):
- bo->page_alignment is in page units
Signed-off-by: Matthew Auld
Cc: Thomas
Move back to the buddy allocator for managing device local memory, and
restore the lost mock selftests. Keep around the range manager related
bits, since we likely need this for managing stolen at some point. For
stolen we also don't need to reserve anything so no need to support a
generic reserve
Now that ttm_resource_manager just returns a generic ttm_resource we
don't need to reference the mm_node stuff anymore which mostly only
makes sense for drm_mm_node. In the next few patches we want switch over
to the ttm_buddy_man which is just another type of ttm_resource so
reflect that in the
From: Thomas Hellström
Instead of relying on a static placement, calculate at get_pages() time.
This should work for LMEM regions and system for now. For stolen we need
to take preallocated range into account. That well be added later.
Instead of relying on a static placement, calculate at
Currently we just ignore the I915_BO_ALLOC_CONTIGUOUS flag, which is
fine since everything is already contiguous with the ttm range manager.
However in the next patch we want to switch over to the ttm buddy
manager, where allocations are by default not contiguous.
v2(Thomas):
- Forward
We need to be able to build an sg table from our list of buddy blocks,
so that we can later plug this into our ttm backend, and replace our use
of the range manager.
Signed-off-by: Matthew Auld
Cc: Thomas Hellström
Reviewed-by: Thomas Hellström
---
drivers/gpu/drm/i915/i915_scatterlist.c | 80
Add back our standalone i915_buddy allocator and integrate it into a
ttm_resource_manager. This will plug into our ttm backend for managing
device local-memory in the next couple of patches.
v2(Thomas):
- Return -ENOSPC from the buddy; ttm expects this in order to
trigger eviction
-
to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/John-C-Harrison-Intel-com/Add-support-for-querying-hw-info-that-UMDs-need/20210616-141805
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: x86_64
On Tue, Jun 15, 2021 at 05:42:13PM -0700, Matt Roper wrote:
> Because Render Power Gating restricts us to just a single subslice as a
> valid steering target for reads of multicast registers in a SUBSLICE
> range, the default steering we setup at init may not lead to a suitable
> target for L3BANK
On Mon, 14 Jun 2021 at 10:22, Matthew Auld wrote:
>
> Purely for CI so we can get some pre-merge results for DG1. This is
> especially useful for cross driver TTM changes where CI can hopefully
> catch regressions. This is similar to how we already handle the DG1
> specific uAPI, which are also
On Tue, Jun 15, 2021 at 05:42:12PM -0700, Matt Roper wrote:
> Although most of our multicast registers are replicated per-subslice, we
> also have a small number of multicast registers that are replicated
> per-l3 bank instead. For both types of multicast registers we need to
> make sure we steer
On Wed, Jun 16, 2021 at 11:48:02AM +0200, Zbigniew Kempczyński wrote:
> For topic/intel-for-CI branch only.
>
> We have established previously we stop using relocations starting
> from gen12 platforms with Tigerlake as an exception. We keep this
> statement but we want to enable relocations
On Wed, Jun 16, 2021 at 01:28:33PM +0100, Matthew Auld wrote:
> The first tracepoint for a request is trace_dma_fence_init which is
> called in the ctor before we have properly setup the request->engine. So
> if it's a non-recycled request the rq->engine might be NULL, or some
> garbage value,
== Series Details ==
Series: drm/i915: Be more gentle with exiting non-persistent context (rev6)
URL : https://patchwork.freedesktop.org/series/89644/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10226_full -> Patchwork_20386_full
-for-dma_fence/20210616-154432
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: sparc-randconfig-s032-20210615 (attached as .config)
compiler: sparc-linux-gcc (GCC) 9.3.0
reproduce:
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin
The first tracepoint for a request is trace_dma_fence_init which is
called in the ctor before we have properly setup the request->engine. So
if it's a non-recycled request the rq->engine might be NULL, or some
garbage value, which leads to a crash.
Since we are not permitted to use
On Tue, Jun 15, 2021 at 04:11:29PM +0200, Greg Kroah-Hartman wrote:
> On Tue, Jun 15, 2021 at 03:35:16PM +0200, Christoph Hellwig wrote:
> > From: Jason Gunthorpe
> >
> > This allows a mdev driver to opt out of using vfio_mdev.c, instead the
> > driver will provide a 'struct mdev_driver' and
Clean up the following includecheck warning:
./drivers/gpu/drm/i915/gt/intel_region_lmem.c: intel_region_lmem.h is
included more than once.
No functional change.
Reported-by: Abaci Robot
Signed-off-by: Jiapeng Chong
---
drivers/gpu/drm/i915/gt/intel_region_lmem.c | 1 -
1 file changed, 1
On Tue, Jun 15, 2021 at 01:35:49PM -0600, Alex Williamson wrote:
> On Tue, 15 Jun 2021 15:35:09 +0200
> Christoph Hellwig wrote:
>
> > This is my alternative take on this series from Jason:
> >
> > https://lore.kernel.org/dri-devel/87czsszi9i@redhat.com/T/
> >
> > The mdev/vfio parts are
Hi Claire,
On Wed, Jun 16, 2021 at 02:21:45PM +0800, Claire Chang wrote:
> This series implements mitigations for lack of DMA access control on
> systems without an IOMMU, which could result in the DMA accessing the
> system memory at unexpected times and/or unexpected addresses, possibly
>
== Series Details ==
Series: drm/i915: Add relocation exceptions for two other platforms (rev7)
URL : https://patchwork.freedesktop.org/series/89594/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10226_full -> Patchwork_20385_full
== Series Details ==
Series: drm/i915: Be more gentle with exiting non-persistent context (rev6)
URL : https://patchwork.freedesktop.org/series/89644/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10226 -> Patchwork_20386
== Series Details ==
Series: drm/i915/gem: Remove duplicated call to ops->pread
URL : https://patchwork.freedesktop.org/series/91561/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10226_full -> Patchwork_20383_full
Summary
On 6/16/21 1:00 PM, Maarten Lankhorst wrote:
Op 15-06-2021 om 15:14 schreef Thomas Hellström:
Introduce a for_i915_gem_ww(){} utility to help make the code
around a ww transaction more readable.
Signed-off-by: Thomas Hellström
Reviewed-by: Matthew Auld
---
Op 15-06-2021 om 15:14 schreef Thomas Hellström:
> Introduce a for_i915_gem_ww(){} utility to help make the code
> around a ww transaction more readable.
>
> Signed-off-by: Thomas Hellström
> Reviewed-by: Matthew Auld
> ---
> drivers/gpu/drm/i915/i915_gem_ww.h | 31
== Series Details ==
Series: drm/i915: Add relocation exceptions for two other platforms (rev7)
URL : https://patchwork.freedesktop.org/series/89594/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10226 -> Patchwork_20385
On Wed, 16 Jun 2021 at 10:04, Daniel Vetter wrote:
>
> Between
>
> commit ae30af84edb5b7cc95485922e43afd909a892e1b
> Author: Maarten Lankhorst
> Date: Tue Mar 23 16:50:00 2021 +0100
>
> drm/i915: Disable userptr pread/pwrite support.
>
> and
>
> commit
On Thu, Jun 10, 2021 at 10:46 PM wrote:
>
> From: John Harrison
>
> Various UMDs need to know the L3 bank count. So add a query API for it.
Please link to both the igt test submission for this (there's not even
a Test-with: on the cover letter) and the merge requests for the
various UMD which
== Series Details ==
Series: drm/i915: Be more gentle with exiting non-persistent context (rev5)
URL : https://patchwork.freedesktop.org/series/89644/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10226 -> Patchwork_20384
From: Tvrtko Ursulin
When a non-persistent context exits we currently mark it as banned in
order to trigger fast termination of any outstanding GPU jobs it may have
left running.
In doing so we apply a very strict 1ms limit in which the left over job
has to preempt before we issues an engine
On 10/06/2021 21:46, john.c.harri...@intel.com wrote:
From: John Harrison
Various UMDs need to know the L3 bank count. So add a query API for it.
Signed-off-by: John Harrison
---
drivers/gpu/drm/i915/gt/intel_gt.c | 15 +++
drivers/gpu/drm/i915/gt/intel_gt.h | 1 +
== Series Details ==
Series: drm/i915: Be more gentle with exiting non-persistent context (rev5)
URL : https://patchwork.freedesktop.org/series/89644/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
e16557e3eeac drm/i915: Be more gentle with exiting non-persistent context
-:66:
For topic/intel-for-CI branch only.
We have established previously we stop using relocations starting
from gen12 platforms with Tigerlake as an exception. We keep this
statement but we want to enable relocations conditionally for
Alderlake S+P under require_force_probe flag set.
Keeping
== Series Details ==
Series: drm/i915/gem: Remove duplicated call to ops->pread
URL : https://patchwork.freedesktop.org/series/91561/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10226 -> Patchwork_20383
Summary
---
to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/John-C-Harrison-Intel-com/Add-support-for-querying-hw-info-that-UMDs-need/20210616-141805
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: i386-defconfig
From: Tvrtko Ursulin
When a non-persistent context exits we currently mark it as banned in
order to trigger fast termination of any outstanding GPU jobs it may have
left running.
In doing so we apply a very strict 1ms limit in which the left over job
has to preempt before we issues an engine
== Series Details ==
Series: drm/i915/gem: Remove duplicated call to ops->pread
URL : https://patchwork.freedesktop.org/series/91561/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
8887e9f43783 drm/i915/gem: Remove duplicated call to ops->pread
-:11: ERROR:GIT_COMMIT_ID: Please
'--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Imre-Deak/drm-i915-Force-a-TypeC-PHY-disconnect-during-suspend-shutdown/20210616-12
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: x86_64-randconfig
Between
commit ae30af84edb5b7cc95485922e43afd909a892e1b
Author: Maarten Lankhorst
Date: Tue Mar 23 16:50:00 2021 +0100
drm/i915: Disable userptr pread/pwrite support.
and
commit 0049b688459b846f819b6e51c24cd0781fcfde41
Author: Matthew Auld
Date: Thu Nov 5 15:49:33 2020 +
On Wed, Jun 16, 2021 at 02:21:54PM +0800, Claire Chang wrote:
> Add the functions, swiotlb_{alloc,free} and is_swiotlb_for_alloc to
> support the memory allocation from restricted DMA pool.
>
> The restricted DMA pool is preferred if available.
>
> Note that since coherent allocation needs
On Wed, Jun 16, 2021 at 02:21:51PM +0800, Claire Chang wrote:
> Propagate the swiotlb_force into io_tlb_default_mem->force_bounce and
> use it to determine whether to bounce the data or not. This will be
> useful later to allow for different pools.
>
> Signed-off-by: Claire Chang
Looks good,
== Series Details ==
Series: Restricted DMA
URL : https://patchwork.freedesktop.org/series/91553/
State : failure
== Summary ==
Applying: swiotlb: Refactor swiotlb init functions
Applying: swiotlb: Refactor swiotlb_create_debugfs
Applying: swiotlb: Set dev->dma_io_tlb_mem to the swiotlb pool
== Series Details ==
Series: Restricted DMA
URL : https://patchwork.freedesktop.org/series/91548/
State : failure
== Summary ==
Applying: swiotlb: Refactor swiotlb init functions
Applying: swiotlb: Refactor swiotlb_create_debugfs
Applying: swiotlb: Set dev->dma_io_tlb_mem to the swiotlb pool
Hi Pekka,
On Mon, Jun 07, 2021 at 11:06:32AM +0300, Pekka Paalanen wrote:
> On Mon, 7 Jun 2021 09:48:05 +0200
> Maxime Ripard wrote:
>
> > I've started to implement this for the raspberrypi some time ago.
> >
> > https://github.com/raspberrypi/linux/pull/4201
> >
> > It's basically two
== Series Details ==
Series: Explicity steer l3bank multicast reads when necessary (rev3)
URL : https://patchwork.freedesktop.org/series/91485/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10226_full -> Patchwork_20380_full
On Tue, Jun 15, 2021 at 09:00:40PM -0300, Jason Gunthorpe wrote:
> On Tue, Jun 15, 2021 at 04:11:29PM +0200, Greg Kroah-Hartman wrote:
> > On Tue, Jun 15, 2021 at 03:35:16PM +0200, Christoph Hellwig wrote:
> > > From: Jason Gunthorpe
> > >
> > > This allows a mdev driver to opt out of using
v12: https://lore.kernel.org/patchwork/cover/1447254/
On Wed, Jun 16, 2021 at 11:52 AM Claire Chang wrote:
>
> This series implements mitigations for lack of DMA access control on
> systems without an IOMMU, which could result in the DMA accessing the
> system memory at unexpected times and/or
If a device is not behind an IOMMU, we look up the device node and set
up the restricted DMA when the restricted-dma-pool is presented.
Signed-off-by: Claire Chang
---
drivers/of/address.c| 33 +
drivers/of/device.c | 3 +++
drivers/of/of_private.h | 6
1 - 100 of 113 matches
Mail list logo
