On 2019/10/21 上午7:41, Parav Pandit wrote:
-Original Message-
From: Jason Wang
Sent: Thursday, October 17, 2019 5:49 AM
To: k...@vger.kernel.org; linux-s...@vger.kernel.org; linux-
ker...@vger.kernel.org; dri-de...@lists.freedesktop.org; intel-
g...@lists.freedesktop.org; intel-gvt-...
On 2019/10/18 下午10:20, Cornelia Huck wrote:
On Thu, 17 Oct 2019 18:48:35 +0800
Jason Wang wrote:
This patch introduces a new mdev transport for virtio. This is used to
use kernel virtio driver to drive the mediated device that is capable
of populating virtqueue directly.
A new virtio-mdev dr
On 2019.10.16 19:39:02 +0100, Chris Wilson wrote:
> Stop trying to escape out of the gvt layer to find the engine that we
> initially setup for use with gvt. Record the engines during initialisation
> and use them henceforth.
>
> add/remove: 1/4 grow/shrink: 22/28 up/down: 341/-1410 (-1069)
>
> S
On 2019/10/18 下午9:30, Cornelia Huck wrote:
On Fri, 18 Oct 2019 18:55:02 +0800
Jason Wang wrote:
On 2019/10/18 下午5:46, Cornelia Huck wrote:
On Thu, 17 Oct 2019 18:48:34 +0800
Jason Wang wrote:
+ * @get_vendor_id: Get virtio vendor id
+ * @mdev: mediat
On 2019.10.16 19:39:01 +0100, Chris Wilson wrote:
> Use the local vgpu_lock while preparing workloads to avoid taking the
> obsolete i915->drm.struct_mutex
>
> Signed-off-by: Chris Wilson
> ---
Looks good to me. Sorry for late reply as just be back from vacation.
Reviewed-by: Zhenyu Wang
> d
== Series Details ==
Series: drm/i915: Try to re-use GOP / previous M-N-P settings for vlv DSI PLL
URL : https://patchwork.freedesktop.org/series/68286/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7136_full -> Patchwork_14898_full
== Series Details ==
Series: kernel-doc: rename the kernel-doc directive 'functions' to 'identifiers'
URL : https://patchwork.freedesktop.org/series/68277/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7136_full -> Patchwork_14896_full
=
== Series Details ==
Series: drm/i915: Extract GT ring management (rev2)
URL : https://patchwork.freedesktop.org/series/68270/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7136 -> Patchwork_14899
Summary
---
**FAILU
== Series Details ==
Series: drm/i915: Extract GT ring management (rev2)
URL : https://patchwork.freedesktop.org/series/68270/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
f012561a7b16 drm/i915: Extract GT ring management
-:49: WARNING:FILE_PATH_CHANGES: added, moved or delete
== Series Details ==
Series: drm/i915: Try to re-use GOP / previous M-N-P settings for vlv DSI PLL
URL : https://patchwork.freedesktop.org/series/68286/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7136 -> Patchwork_14898
== Series Details ==
Series: series starting with [1/3] dma-buf: Prettify typecasts for
dma-fence-chain
URL : https://patchwork.freedesktop.org/series/68274/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7136_full -> Patchwork_14895_full
==
From: Andi Shyti
Although the ring management is much smaller compared to the other GT
power management functions, continue the theme of extracting it out of
the huge intel_pm.c for maintenance.
Based on a patch by Chris Wilson.
Signed-off-by: Andi Shyti
Cc: Chris Wilson
Reviewed-by: Chris Wi
== Series Details ==
Series: kernel-doc: rename the kernel-doc directive 'functions' to 'identifiers'
URL : https://patchwork.freedesktop.org/series/68277/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7136 -> Patchwork_14896
===
== Series Details ==
Series: drm/i915: Program LUT before intel_color_commit() if LUT was not
previously set
URL : https://patchwork.freedesktop.org/series/68278/
State : failure
== Summary ==
Applying: drm/i915: Program LUT before intel_color_commit() if LUT was not
previously set
Using ind
Fastboot is not working on an Asus T100HA, it gives the following
relevant messages / errors:
dsi pll div 000201e6, ctrl 80080100
fastset mismatch in dsi_pll.ctrl (expected 0x80100100, found 0x80080100)
fastset mismatch in dsi_pll.div (expected 0x0002008e, found 0x000201e6)
The problem seems t
Since commit 051a6d8d3ca0 ("drm/i915: Move LUT programming to happen after
vblank waits"), I am seeing an ugly colored flash of the first few display
lines on 2 Cherry Trail devices when the gamma table gets set for the first
time. A blue flash on a GPD win and a yellow flash on an Asus T100HA.
Th
== Series Details ==
Series: kernel-doc: rename the kernel-doc directive 'functions' to 'identifiers'
URL : https://patchwork.freedesktop.org/series/68277/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
5c039a1a525e kernel-doc: rename the kernel-doc directive 'functions' to
'id
The 'functions' directive is not only for functions, but also works for
structs/unions. So the name is misleading. This patch renames it to
'identifiers', which specific the functions/types to be included in
documentation. We keep the old name as an alias of the new one before
all documentation are
== Series Details ==
Series: series starting with [1/3] dma-buf: Prettify typecasts for
dma-fence-chain
URL : https://patchwork.freedesktop.org/series/68274/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7136 -> Patchwork_14895
== Series Details ==
Series: series starting with [1/3] dma-buf: Prettify typecasts for
dma-fence-chain
URL : https://patchwork.freedesktop.org/series/68274/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
2de26a630d27 dma-buf: Prettify typecasts for dma-fence-chain
aa2250c9512d
A few very simple testcases to exercise the dma-fence-chain API.
Signed-off-by: Chris Wilson
---
drivers/dma-buf/Makefile | 3 +-
drivers/dma-buf/selftests.h | 1 +
drivers/dma-buf/st-dma-fence-chain.c | 713 +++
3 files changed, 716 insertions(+)
Inside dma-fence-chain, we use a cmpxchg on an RCU-protected pointer. To
avoid the sparse warning for using the RCU pointer directly, we have to
cast away the __rcu annotation. However, we don't need to use void*
everywhere and can stick to the dma_fence*.
Signed-off-by: Chris Wilson
---
drivers
Whenever we walk along the dma-fence-chain, we prune signaled links to
keep the chain nice and tidy. This leads to situations where we can
prune a link and report the earlier fence as the target seqno --
violating our own consistency checks that the seqno is not more advanced
than the last element
Quoting Andi Shyti (2019-10-20 01:50:45)
> From: Andi Shyti
>
> Although the ring management is much smaller compared to the other GT
> power management functions, continue the theme of extracting it out of
> the huge intel_pm.c for maintenance.
>
> Based on a patch by Chris Wilson.
>
> Signed-
Quoting Lionel Landwerlin (2019-10-19 22:46:47)
> The current logic just reapplies the same configuration already stored
> into stream->oa_config instead of the newly selected one.
>
> Signed-off-by: Lionel Landwerlin
> Fixes: 7831e9a965ea ("drm/i915/perf: Allow dynamic reconfiguration of the OA
25 matches
Mail list logo