Hi Zhi,
Daniel asked few weeks ago about the scripts that you run there,
but I didn't see any follow-up.
I don't understand why yet, but apparently gvt pull request
is not going to patchwork so dim is not able to add the "Link:"
hence end up without mandatory patchwork links.
Last round I by-pass dim and move forward even without the "Link:"
if the solution is easier I'd like to do the right thing this time.
Although I'm open to by-pass again,
I'd like to know if we are in sync to understand what is happening
again and get that fixed for next time
Cc: Daniel in case he know a quick fix or can at least provide more
info there on what could be failing.
Thanks,
Rodrigo.
On Tue, Feb 06, 2018 at 08:36:49AM +0000, Zhi Wang wrote:
> Hi guys:
> Here are the latest gvt-next-fixes pull. It contains vGPU reset
> enhancement, which refines vGPU reset flow and the support of virtual
> aperture read/write when x-no-mmap=on is set in KVM, which is required by a
> test case from Redhat and also another fix for virtual OpRegion.
>
> Thanks,
> Zhi.
>
> The following changes since commit 751b01cb07ebf0dbbe4a4fbfeaa509388e4a2b0a:
>
> drm/i915/ppgtt: Pin page directories before allocation (2018-02-01
> 07:33:04 -0800)
>
> are available in the git repository at:
>
> http://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2018-02-04
>
> for you to fetch changes up to 47419494f216812b42f5d1c5a2984cd46253b4cc:
>
> drm/i915/gvt: Use KVM r/w to access guest opregion (2018-02-06 13:14:47
> +0800)
>
> ----------------------------------------------------------------
> - vGPU reset refinement. (Weinan)
> - Support aperture read/write emulation when x-no-mmap=on. (Changbin)
> - Use guest memory read/write in GVT MPT to access OpRegion. (Tina)
>
> ----------------------------------------------------------------
> Changbin Du (1):
> drm/i915/gvt: Fix aperture read/write emulation when enable
> x-no-mmap=on
>
> Tina Zhang (1):
> drm/i915/gvt: Use KVM r/w to access guest opregion
>
> Weinan Li (2):
> drm/i915/gvt: refine intel_vgpu_submission_ops as per engine ops
> drm/i915/gvt: only reset execlist state of one engine during VM engine
> reset
>
> drivers/gpu/drm/i915/gvt/cfg_space.c | 15 +----
> drivers/gpu/drm/i915/gvt/execlist.c | 22 ++++----
> drivers/gpu/drm/i915/gvt/gvt.h | 6 +-
> drivers/gpu/drm/i915/gvt/handlers.c | 7 +--
> drivers/gpu/drm/i915/gvt/kvmgt.c | 36 +++++++++++-
> drivers/gpu/drm/i915/gvt/mmio.c | 42 --------------
> drivers/gpu/drm/i915/gvt/opregion.c | 98
> +++++++++++++++++++++++----------
> drivers/gpu/drm/i915/gvt/sched_policy.c | 14 ++++-
> drivers/gpu/drm/i915/gvt/scheduler.c | 19 ++++---
> drivers/gpu/drm/i915/gvt/scheduler.h | 1 +
> drivers/gpu/drm/i915/gvt/vgpu.c | 3 +-
> 11 files changed, 144 insertions(+), 119 deletions(-)
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
