Re: [Intel-gfx] [PULL] gvt-next-fixes for 4.16

Zhenyu Wang writes: > On 2018.02.06 11:45:04 -0800, Rodrigo Vivi wrote: >> >> 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

Re: [Intel-gfx] [PULL] gvt-next-fixes for 4.16

On 2018.02.06 11:45:04 -0800, Rodrigo Vivi wrote: > > 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:"

Re: [Intel-gfx] [PULL] gvt-next-fixes for 4.16

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

[Intel-gfx] [PULL] gvt-next-fixes for 4.16

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.

Re: [Intel-gfx] [PULL] gvt-next fixes for 4.16

On Thu, Jan 18, 2018 at 02:23:13AM +, Zhenyu Wang wrote: > On 2018.01.17 08:03:49 -0800, Rodrigo Vivi wrote: > > > > > > Zhenyu Wang (2): > > > drm/i915/gvt: cancel virtual vblank timer when no vGPU exists > > > drm/i915/gvt: cancel scheduler timer when no vGPU exists > > > >

Re: [Intel-gfx] [PULL] gvt-next fixes for 4.16

On 2018.01.17 08:03:49 -0800, Rodrigo Vivi wrote: > > > > Zhenyu Wang (2): > > drm/i915/gvt: cancel virtual vblank timer when no vGPU exists > > drm/i915/gvt: cancel scheduler timer when no vGPU exists > > dim: ERROR: 0eb582541cfd7a17b6fcf9282c966c0e59efd02f is lacking mandatory >

Re: [Intel-gfx] [PULL] gvt-next fixes for 4.16

On 2018.01.17 08:03:49 -0800, Rodrigo Vivi wrote: > > dim: ERROR: 0eb582541cfd7a17b6fcf9282c966c0e59efd02f is lacking mandatory > review, aborting > > Is it possible to get someone to quickly review it and fix the original > commit, like last time? > Hi, Rodrigo Zhi has quickly helped to

Re: [Intel-gfx] [PULL] gvt-next fixes for 4.16

On Wed, Jan 17, 2018 at 04:23:48AM +, Zhenyu Wang wrote: > > Hi, > > Here's queued gvt-next fixes for 4.16-rc1. Mostly with regression > fixes on vGPU display dmabuf, mmio switch and other misc changes, > details below. > > thanks > -- > The following changes since commit

[Intel-gfx] [PULL] gvt-next fixes for 4.16

Hi, Here's queued gvt-next fixes for 4.16-rc1. Mostly with regression fixes on vGPU display dmabuf, mmio switch and other misc changes, details below. thanks -- The following changes since commit 4fafba2d73fcaf1b433c26e753a98ad4b231754a: drm/i915/gvt: move write protect handler out of mmio