== Series Details ==
Series: drm/i915/gvt: Deliver guest cursor hotspot info (rev3)
URL : https://patchwork.freedesktop.org/series/41727/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4172 -> Patchwork_8992 =
== Summary - WARNING ==
Minor unknown changes coming with Patc
Guest OS driver uses PV info registers to deliver cursor hotspot info
to host. This patch is used to get cursor hotspot info from virtual
registers and deliver it to host userspace.
v4->v5:
- remove CI warning.
v3->v4:
- return UINT_MAX when x_hot/y_hot is invalid. (Zhenyu)
- correct version.
v2
== Series Details ==
Series: drm/i915/psr: vbt change for psr (rev7)
URL : https://patchwork.freedesktop.org/series/41289/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_4172_full -> Patchwork_8991_full =
== Summary - FAILURE ==
Serious unknown changes coming with Patchwo
== Series Details ==
Series: drm/i915/psr: vbt change for psr (rev7)
URL : https://patchwork.freedesktop.org/series/41289/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4172 -> Patchwork_8991 =
== Summary - WARNING ==
Minor unknown changes coming with Patchwork_8991 need
== Series Details ==
Series: drm/i915/psr: vbt change for psr (rev7)
URL : https://patchwork.freedesktop.org/series/41289/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
e221e68c5170 drm/i915/psr: vbt change for psr
-:71: CHECK:SPACING: spaces preferred around that '<<' (ctx:VxV
From: Vathsala Nagaraju
For psr block #9, the vbt description has moved to options [0-3] for
TP1,TP2,TP3 Wakeup time from decimal value without any change to vbt
structure. Since spec does not mention from which VBT version this
change was added to vbt.bsf file, we cannot depend on bdb->version
The following changes since commit 0c79f9cb77eae28d48a4f9fc1b3341aacbbd260c:
drm/i915/gen9: Add WaClearHIZ_WM_CHICKEN3 for bxt and glk (2018-05-13
10:29:44 +0100)
are available in the git repository at:
https://github.com/intel/gvt-linux.git tags/gvt-next-2018-05-14
for you to fetch chan
== Series Details ==
Series: drm/i915: Shrink search list for active timelines
URL : https://patchwork.freedesktop.org/series/43102/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4172_full -> Patchwork_8990_full =
== Summary - WARNING ==
Minor unknown changes coming with
== Series Details ==
Series: drm/i915: Shrink search list for active timelines
URL : https://patchwork.freedesktop.org/series/43102/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4172 -> Patchwork_8990 =
== Summary - WARNING ==
Minor unknown changes coming with Patchwork
When switching to the kernel context, we force the switch to occur after
all currently active requests (so that we know the GPU won't switch
immediately away and the kernel context remains current as we work). To
do so we have to inspect all the timelines and add a fence from the
active work to que
== Series Details ==
Series: series starting with [1/3] drm/i915: Track the purgeable objects on a
separate eviction list
URL : https://patchwork.freedesktop.org/series/43101/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4172_full -> Patchwork_8989_full =
== Summary - WAR
== Series Details ==
Series: series starting with [1/3] drm/i915: Track the purgeable objects on a
separate eviction list
URL : https://patchwork.freedesktop.org/series/43101/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4172 -> Patchwork_8989 =
== Summary - WARNING ==
== Series Details ==
Series: series starting with [1/3] drm/i915: Track the purgeable objects on a
separate eviction list
URL : https://patchwork.freedesktop.org/series/43101/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Commit: drm/i915: Track the purgeable objects on a separate
== Series Details ==
Series: series starting with [1/3] drm/i915: Track the purgeable objects on a
separate eviction list
URL : https://patchwork.freedesktop.org/series/43101/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
5c868b886aba drm/i915: Track the purgeable objects on a
Currently the purgeable objects, I915_MADV_DONTNEED, as mixed in the
normal bound/unbound lists. Every shrinker pass starts with an attempt
to purge from this set of unneeded objects, which entails us doing a
walk over both lists looking for any candidates. If there are none, and
since we are shrin
Currently, we try to report to the shrinker the precise number of
objects (pages) that are available to be reaped at this moment. This
requires searching all objects with allocated pages to see if they
fulfill the search criteria, and this count is performed quite
frequently. (The shrinker tries to
As i915_gem_object_phys_attach() wants to play dirty and mess around
with obj->mm.pages itself (replacing the shmemfs with a DMA allocation),
refactor the gubbins so into i915_gem_object_unset_pages() that we don't
have to duplicate all the secrets.
Signed-off-by: Chris Wilson
Cc: Joonas Lahtinen
Quoting Michel Thierry (2018-05-11 16:07:55)
> On 5/11/2018 5:43 AM, Mika Kuoppala wrote:
> > Chris Wilson writes:
> >
> >> Quoting Mika Kuoppala (2018-05-11 10:56:49)
> >>> Michel Thierry writes:
> >>>
> Factor in clear values wherever required while updating destination
> min/max.
>
Quoting Chris Wilson (2018-05-11 10:58:36)
> Quoting Matthew Auld (2018-05-11 10:51:40)
> > We write all 4K page entries, even when using 64K pages. In order to
> > verify that the HW isn't cheating by using the 4K PTE instead of the 64K
> > PTE, we want to remove all the surplus entries. If the HW
== Series Details ==
Series: series starting with [1/4] drm/mm: Reject over-sized allocation
requests early
URL : https://patchwork.freedesktop.org/series/43097/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4171_full -> Patchwork_8987_full =
== Summary - WARNING ==
Min
== Series Details ==
Series: series starting with [1/2] drm/i915: Track the purgeable objects on a
separate eviction list
URL : https://patchwork.freedesktop.org/series/43098/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_4171 -> Patchwork_8988 =
== Summary - FAILURE ==
== Series Details ==
Series: series starting with [1/2] drm/i915: Track the purgeable objects on a
separate eviction list
URL : https://patchwork.freedesktop.org/series/43098/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Commit: drm/i915: Track the purgeable objects on a separate
Currently the purgeable objects, I915_MADV_DONTNEED, as mixed in the
normal bound/unbound lists. Every shrinker pass starts with an attempt
to purge from this set of unneeded objects, which entails us doing a
walk over both lists looking for any candidates. If there are none, and
since we are shrin
Currently, we try to report to the shrinker the precise number of
objects (pages) that are available to be reaped at this moment. This
requires searching all objects with allocated pages to see if they
fulfill the search criteria, and this count is performed quite
frequently. (The shrinker tries to
== Series Details ==
Series: series starting with [1/4] drm/mm: Reject over-sized allocation
requests early
URL : https://patchwork.freedesktop.org/series/43097/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4171 -> Patchwork_8987 =
== Summary - WARNING ==
Minor unknown
Searching for an available hole by address is slow, as there no
guarantee that a hole will be available and so we must walk over all
nodes in the rbtree before we determine the search was futile. In many
cases, the caller doesn't strictly care for the highest available hole
and was just opportunist
If we can use an unmappable ring, try to pin it out of the mappable
aperture. This simple layout preference is to try and keep the mappable
aperture reserved and available to handle GGTT mmapping requests from
userspace without causing evictions and GPU stalls.
Signed-off-by: Chris Wilson
Cc: Joo
As we keep an rbtree of available holes sorted by their size, we can
very easily determine if there is any hole large enough that might
satisfy the allocation request. This helps when dealing with a highly
fragmented address space and a request for a search by address.
To cache the largest size, w
To no surprise (since we've flip-flopped over the use of PIN_HIGH a few
times), doing a search by address over a pathologically fragmented
address space is exceeding slow. To protect ourselves from nearly
unbounded latency (think searching a million holes while under
struct_mutex), limit the search
29 matches
Mail list logo
