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

Hi, Here's one single change for gvt to use idr based dmabuf object reference instead of old adhoc code. We've verified no regression for internal test. Thanks. -- The following changes since commit d944eafed618a8507270b324ad9d5405bb7f0b3e: drm/i915: Check pipe source size when using skl+

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

On Thu, 23 Feb 2023, Zhenyu Wang wrote: > Hi, > > This is what are on gvt tree now for next kernel, including fixes for > gvt debugfs, one kconfig symbol fix for menu presentation and misc > typo fixes. Please check details below. This is generated against current > drm-intel-next-fixes. Thanks,

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

Hi, This is what are on gvt tree now for next kernel, including fixes for gvt debugfs, one kconfig symbol fix for menu presentation and misc typo fixes. Please check details below. This is generated against current drm-intel-next-fixes. Thanks! -- The following changes since commit

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

On Thu, 29 Apr 2021, Zhenyu Wang wrote: > Hi, > > Here's just another left fix for possible divide error in vgpu > display rate calculation by Colin. Thanks, pulled to drm-intel-next-fixes. > btw, I'll need a backmerge of linus tree or maybe wait till rc1 > to apply gvt mdev dependency fix from

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

Hi, Here's just another left fix for possible divide error in vgpu display rate calculation by Colin. btw, I'll need a backmerge of linus tree or maybe wait till rc1 to apply gvt mdev dependency fix from https://patchwork.freedesktop.org/series/89479/ Thanks -- The following changes since

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

On Wed, 21 Apr 2021, Zhenyu Wang wrote: > Hi, > > Here're queued gvt-next-fixes changes. Two ones are for code cleanup > on unused function or duplicated function call, with another one for > consistent function return type. Thanks, pulled to drm-intel-next-fixes. BR, Jani. > > Thanks. > -- >

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

Hi, Here're queued gvt-next-fixes changes. Two ones are for code cleanup on unused function or duplicated function call, with another one for consistent function return type. Thanks. -- The following changes since commit d153e8c156dafeb847fd655f416cf81c007e8706: Merge tag

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

On Mon, Feb 22, 2021 at 04:34:02PM +0800, Zhenyu Wang wrote: > > Hi, > > Looks last gvt pull missed -gt-next window before CNY holiday. > So here're left three changes for fixing ww locking, cmd parser > fix for i915 state use and one left cleanup fix. no problem at all. I believe we still have

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

Hi, Looks last gvt pull missed -gt-next window before CNY holiday. So here're left three changes for fixing ww locking, cmd parser fix for i915 state use and one left cleanup fix. Thanks! -- The following changes since commit 81ce8f04aa96f7f6cae05770f68b5d15be91f5a2: drm/i915/gt: Correct

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

On Tue, Jan 05, 2021 at 10:36:54AM +0200, Jani Nikula wrote: > On Tue, 05 Jan 2021, Zhenyu Wang wrote: > > Ping... > > I suppose this should be merged to drm-intel-next (or drm-intel-gt-next, > or both). It was too late for next-fixes, and it's really not the kind > of fixes we need to queue to

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

On Tue, 05 Jan 2021, Zhenyu Wang wrote: > Ping... I suppose this should be merged to drm-intel-next (or drm-intel-gt-next, or both). It was too late for next-fixes, and it's really not the kind of fixes we need to queue to v5.11-rc's. Rodrigo? BR, Jani. > > On 2020.12.25 10:20:09 +0800,

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

Ping... On 2020.12.25 10:20:09 +0800, Zhenyu Wang wrote: > > Hi, > > Here's queued fixes from Jani for one useless inline and fix > CONFIG_DRM_I915_WERROR for gvt headers. > > Thanks and Merry Christmas! > -- > The following changes since commit 9a3a238b3de97b4210c6de66aa88b2d7021ac086: > >

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

Hi, Here's queued fixes from Jani for one useless inline and fix CONFIG_DRM_I915_WERROR for gvt headers. Thanks and Merry Christmas! -- The following changes since commit 9a3a238b3de97b4210c6de66aa88b2d7021ac086: drm/i915/gvt: treat intel_gvt_mpt as const in gvt code (2020-11-23 17:14:20

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

On Wed, 05 Aug 2020, Zhenyu Wang wrote: > Hi, > > Here's to only include gvt fixes for 5.9-rc1. Two fixes to make > guest suspend/resume working gracefully are included. Pulled, thanks. BR, Jani. -- Jani Nikula, Intel Open Source Graphics Center ___

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

Hi, Here's to only include gvt fixes for 5.9-rc1. Two fixes to make guest suspend/resume working gracefully are included. Thanks -- The following changes since commit e57bd05ec0d2d82d63725dedf9f5a063f879de25: drm/i915: Update DRIVER_DATE to 20200715 (2020-07-15 14:18:02 +0300) are

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

Quoting Zhenyu Wang (2020-05-28 06:35:59) > > Hi, > > Here's two queued warning fixes for gvt-next. One is for clang warning > on debug only function and another one from coccicheck to use ARRAY_SIZE. Pulled now, thanks for the PR. Regards, Joonas > > Thanks > -- > The following changes

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

Hi, Here's two queued warning fixes for gvt-next. One is for clang warning on debug only function and another one from coccicheck to use ARRAY_SIZE. Thanks -- The following changes since commit 3a36aa237e4ed04553c0998cf5f47eda3e206e4f: drm/i915: Update DRIVER_DATE to 20200515 (2020-05-15

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

On 2020.04.07 16:53:19 +0300, Jani Nikula wrote: > On Tue, 07 Apr 2020, Rodrigo Vivi wrote: > > On Tue, Apr 07, 2020 at 04:02:56PM +0800, Zhenyu Wang wrote: > >> On 2020.04.03 10:50:33 -0700, Rodrigo Vivi wrote: > >> > > >> > +Dave and Daniel, > >> > > >> > > > >> > > I forgot to mention one

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

On Tue, 07 Apr 2020, Rodrigo Vivi wrote: > On Tue, Apr 07, 2020 at 04:02:56PM +0800, Zhenyu Wang wrote: >> On 2020.04.03 10:50:33 -0700, Rodrigo Vivi wrote: >> > >> > +Dave and Daniel, >> > >> > > >> > > I forgot to mention one thing for 5.7. We've fixed to change guest mem >> > > r/w >> > >

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

On Tue, Apr 07, 2020 at 04:02:56PM +0800, Zhenyu Wang wrote: > On 2020.04.03 10:50:33 -0700, Rodrigo Vivi wrote: > > > > +Dave and Daniel, > > > > > > > > I forgot to mention one thing for 5.7. We've fixed to change guest mem r/w > > > from KVM to use new VFIO dma r/w instead in this series: >

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

On 2020.04.03 10:50:33 -0700, Rodrigo Vivi wrote: > > +Dave and Daniel, > > > > > I forgot to mention one thing for 5.7. We've fixed to change guest mem r/w > > from KVM to use new VFIO dma r/w instead in this series: > > https://patchwork.freedesktop.org/series/72038/ > > > > As this depends

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

+Dave and Daniel, On Fri, Apr 03, 2020 at 11:05:07AM +0800, Zhenyu Wang wrote: > On 2020.03.31 09:26:44 -0700, Rodrigo Vivi wrote: > > On Tue, Mar 31, 2020 at 03:00:25PM +0800, Zhenyu Wang wrote: > > > > > > Hi, > > > > > > Here's more queued gvt fixes for 5.7. Please see details below. > > >

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

On 2020.03.31 09:26:44 -0700, Rodrigo Vivi wrote: > On Tue, Mar 31, 2020 at 03:00:25PM +0800, Zhenyu Wang wrote: > > > > Hi, > > > > Here's more queued gvt fixes for 5.7. Please see details below. > > > > Thanks > > -- > > The following changes since commit

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

On Tue, Mar 31, 2020 at 03:00:25PM +0800, Zhenyu Wang wrote: > > Hi, > > Here's more queued gvt fixes for 5.7. Please see details below. > > Thanks > -- > The following changes since commit a61ac1e75105a077ec1efd6923ae3c619f862304: > > drm/i915/gvt: Wean gvt off using dev_priv (2020-03-06

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

Hi, Here's more queued gvt fixes for 5.7. Please see details below. Thanks -- The following changes since commit a61ac1e75105a077ec1efd6923ae3c619f862304: drm/i915/gvt: Wean gvt off using dev_priv (2020-03-06 10:08:10 +0800) are available in the Git repository at:

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

On 2019.12.05 10:14:35 +0200, Joonas Lahtinen wrote: > Quoting Zhenyu Wang (2019-12-05 08:11:41) > > > > ping.. > > This was pulled, but my dim push was interrupted so I had to re-push and > wait for CI results. Looks all good. Thanks for the PR. > > Do you have a plan to start adding Fixes:

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

Quoting Zhenyu Wang (2019-12-05 08:11:41) > > ping.. This was pulled, but my dim push was interrupted so I had to re-push and wait for CI results. Looks all good. Thanks for the PR. Do you have a plan to start adding Fixes: and Link: tags to the GVT commits? Regards, Joonas

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

ping.. On 2019.12.02 13:17:11 +0800, Zhenyu Wang wrote: > > Hi, > > More gvt fixes for 5.5-rc. One is MI_ATOMIC cmd parser fix which > missed 5.4 and another two for CFL non-priv reg access fixes. > > Thanks > -- > The following changes since commit 83faaf074e6d1ca4d1441aded0d3f01bce413479: >

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

Hi, More gvt fixes for 5.5-rc. One is MI_ATOMIC cmd parser fix which missed 5.4 and another two for CFL non-priv reg access fixes. Thanks -- The following changes since commit 83faaf074e6d1ca4d1441aded0d3f01bce413479: drm/i915/gvt: Stop initializing pvinfo through reading mmio (2019-11-08

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

Quoting Zhenyu Wang (2019-11-12 08:20:32) > > Hi, > > Here's one fix to remove PVINFO read in initial state for extra > warning messages in debug. Pulled now. Regards, Joonas ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org

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

Hi, Here's one fix to remove PVINFO read in initial state for extra warning messages in debug. Thanks -- The following changes since commit d9dace9438945e7c13d91e62927c5c6c88a37ee5: drm/i915/selftests: Add intel_gt_suspend_prepare (2019-11-05 16:06:25 +0200) are available in the Git

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

On Mon, 2019-09-09 at 15:35 -0700, Rodrigo Vivi wrote: > On Mon, Sep 09, 2019 at 02:54:59PM -0700, Vetter, Daniel wrote: > > On Mon, 2019-09-09 at 10:24 -0700, Rodrigo Vivi wrote: > > > Hi guys, > > > > > > On Fri, Sep 06, 2019 at 01:42:55PM +0800, Zhenyu Wang wrote: > > > > Hi, > > > > > > > >

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

On 2019.09.09 15:35:10 -0700, Rodrigo Vivi wrote: > On Mon, Sep 09, 2019 at 02:54:59PM -0700, Vetter, Daniel wrote: > > On Mon, 2019-09-09 at 10:24 -0700, Rodrigo Vivi wrote: > > > Hi guys, > > > > > > On Fri, Sep 06, 2019 at 01:42:55PM +0800, Zhenyu Wang wrote: > > > > Hi, > > > > > > > >

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

On Mon, Sep 09, 2019 at 02:54:59PM -0700, Vetter, Daniel wrote: > On Mon, 2019-09-09 at 10:24 -0700, Rodrigo Vivi wrote: > > Hi guys, > > > > On Fri, Sep 06, 2019 at 01:42:55PM +0800, Zhenyu Wang wrote: > > > Hi, > > > > > > Here's gvt-next-fixes with two recent fixes, one for recent > > > guest

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

On Mon, 2019-09-09 at 10:24 -0700, Rodrigo Vivi wrote: > Hi guys, > > On Fri, Sep 06, 2019 at 01:42:55PM +0800, Zhenyu Wang wrote: > > Hi, > > > > Here's gvt-next-fixes with two recent fixes, one for recent > > guest hang regression and another for guest reset fix. > > > > Thanks. > > -- > >

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

Hi guys, On Fri, Sep 06, 2019 at 01:42:55PM +0800, Zhenyu Wang wrote: > > Hi, > > Here's gvt-next-fixes with two recent fixes, one for recent > guest hang regression and another for guest reset fix. > > Thanks. > -- > The following changes since commit c36beba6b296b3c05a0f29753b04775e5ae23886:

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

On Fri, Sep 06, 2019 at 01:42:55PM +0800, Zhenyu Wang wrote: > > Hi, > > Here's gvt-next-fixes with two recent fixes, one for recent > guest hang regression and another for guest reset fix. > > Thanks. > -- > The following changes since commit c36beba6b296b3c05a0f29753b04775e5ae23886: > >

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

Hi, Here's gvt-next-fixes with two recent fixes, one for recent guest hang regression and another for guest reset fix. Thanks. -- The following changes since commit c36beba6b296b3c05a0f29753b04775e5ae23886: drm/i915: Seal races between async GPU cancellation, retirement and signaling

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

Thanks, pulled this now. Regards, Joonas Quoting Zhenyu Wang (2019-05-07 12:05:58) > > Hi, > > Here's gvt-next-fixes for 5.2-rc, which includes one revert for BXT > regression, one missed context mmio reg after RCS renaming, sanitize > display buffer size calculation and some klocwork

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

Hi, Here's gvt-next-fixes for 5.2-rc, which includes one revert for BXT regression, one missed context mmio reg after RCS renaming, sanitize display buffer size calculation and some klocwork warning/error fixes. Thanks -- The following changes since commit

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

Quoting Zhenyu Wang (2018-10-26 09:43:20) > On 2018.10.25 16:07:14 +0300, Joonas Lahtinen wrote: > > Quoting Zhenyu Wang (2018-10-23 06:46:59) > > > > > > Hi, > > > > > > Here's gvt-next-fixes for 4.20 with three changes. Mostly > > > to fix possible arbitrary update on guest GGTT entry and > >

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

On 2018.10.25 16:07:14 +0300, Joonas Lahtinen wrote: > Quoting Zhenyu Wang (2018-10-23 06:46:59) > > > > Hi, > > > > Here's gvt-next-fixes for 4.20 with three changes. Mostly > > to fix possible arbitrary update on guest GGTT entry and > > with proper invalidate of old entry. Another one for one

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

On 2018.10.25 11:28:28 -0700, Rodrigo Vivi wrote: > On Thu, Oct 25, 2018 at 04:07:14PM +0300, Joonas Lahtinen wrote: > > Quoting Zhenyu Wang (2018-10-23 06:46:59) > > > > > > Hi, > > > > > > Here's gvt-next-fixes for 4.20 with three changes. Mostly > > > to fix possible arbitrary update on guest

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

On Thu, Oct 25, 2018 at 04:07:14PM +0300, Joonas Lahtinen wrote: > Quoting Zhenyu Wang (2018-10-23 06:46:59) > > > > Hi, > > > > Here's gvt-next-fixes for 4.20 with three changes. Mostly > > to fix possible arbitrary update on guest GGTT entry and > > with proper invalidate of old entry. Another

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

Quoting Zhenyu Wang (2018-10-23 06:46:59) > > Hi, > > Here's gvt-next-fixes for 4.20 with three changes. Mostly > to fix possible arbitrary update on guest GGTT entry and > with proper invalidate of old entry. Another one for one > chicken reg mask fix. > > thanks Hi, DIM seems to be

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

Hi, Here's gvt-next-fixes for 4.20 with three changes. Mostly to fix possible arbitrary update on guest GGTT entry and with proper invalidate of old entry. Another one for one chicken reg mask fix. thanks -- The following changes since commit 835fe6d75d14c1513910ed7f5665127fee12acc8:

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

On Tue, Aug 14, 2018 at 03:31:40PM +0800, Zhenyu Wang wrote: > > Hi, > > This is initial gvt fixes for 4.19 with some accumulated fixes, > pls check details below. pulled, thanks. > > Thanks > -- > The following changes since commit 3237c0dbe21f8d2ca2feaa3891aff3619873cd30: > >

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

Hi, This is initial gvt fixes for 4.19 with some accumulated fixes, pls check details below. Thanks -- The following changes since commit 3237c0dbe21f8d2ca2feaa3891aff3619873cd30: drm/i915/kvmgt: Fix compilation error (2018-08-06 11:28:35 -0700) are available in the Git repository at:

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

Quoting Zhenyu Wang (2018-03-20 04:41:08) > > Hi, Joonas > > Here's gvt-next-fixes update for 4.17. One regression that > caused guest VM gpu hang has been fixed and with other changes > as details below. Pulled, thanks. Regards, Joonas ___ Intel-gfx

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

Hi, Joonas Here's gvt-next-fixes update for 4.17. One regression that caused guest VM gpu hang has been fixed and with other changes as details below. Thanks -- The following changes since commit 22de4e7a531b623962e62ee6d3a39a7e51bdf90e: drm/i915/pmu: Work around compiler warnings on some

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