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

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

[Zhenyu Wang]

[-- Attachment #1.1: Type: text/plain, Size: 1981 bytes --]


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 +0800)

are available in the Git repository at:

  https://github.com/intel/gvt-linux tags/gvt-next-fixes-2020-12-25

for you to fetch changes up to e056f669dbf76b8752b6cb0b8edd2f75cbdcabb1:

  drm/i915/gvt: make mpt.h self-contained (2020-12-22 11:41:35 +0800)

----------------------------------------------------------------
gvt-next-fixes-2020-12-25

- Avoid one useless inline (Jani)
- make gvt header self-contained, fix CONFIG_DRM_I915_WERROR (Jani)

----------------------------------------------------------------
Jani Nikula (9):
      drm/i915/gvt: avoid useless use of inline
      drm/i915/gvt: make execlist.h self-contained
      drm/i915/gvt: make fb_decoder.h self-contained
      drm/i915/gvt: make gtt.h self-contained
      drm/i915/gvt: make interrupt.h self-contained
      drm/i915/gvt: make mmio_context.h self-contained
      drm/i915/gvt: make gvt.h self-contained
      drm/i915/gvt: make scheduler.h self-contained
      drm/i915/gvt: make mpt.h self-contained

 drivers/gpu/drm/i915/Makefile           | 10 +---------
 drivers/gpu/drm/i915/gvt/execlist.h     |  3 ---
 drivers/gpu/drm/i915/gvt/fb_decoder.h   |  6 ++++--
 drivers/gpu/drm/i915/gvt/gtt.h          | 11 ++++++++++-
 drivers/gpu/drm/i915/gvt/gvt.h          |  4 ++++
 drivers/gpu/drm/i915/gvt/handlers.c     |  3 +--
 drivers/gpu/drm/i915/gvt/interrupt.h    |  5 ++++-
 drivers/gpu/drm/i915/gvt/mmio_context.h | 11 +++++++++++
 drivers/gpu/drm/i915/gvt/mpt.h          |  2 ++
 drivers/gpu/drm/i915/gvt/scheduler.h    |  5 +++++
 10 files changed, 42 insertions(+), 18 deletions(-)

-- 

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Zhenyu Wang]

[-- Attachment #1.1: Type: text/plain, Size: 2394 bytes --]


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:
> 
>   drm/i915/gvt: treat intel_gvt_mpt as const in gvt code (2020-11-23 17:14:20 +0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux tags/gvt-next-fixes-2020-12-25
> 
> for you to fetch changes up to e056f669dbf76b8752b6cb0b8edd2f75cbdcabb1:
> 
>   drm/i915/gvt: make mpt.h self-contained (2020-12-22 11:41:35 +0800)
> 
> ----------------------------------------------------------------
> gvt-next-fixes-2020-12-25
> 
> - Avoid one useless inline (Jani)
> - make gvt header self-contained, fix CONFIG_DRM_I915_WERROR (Jani)
> 
> ----------------------------------------------------------------
> Jani Nikula (9):
>       drm/i915/gvt: avoid useless use of inline
>       drm/i915/gvt: make execlist.h self-contained
>       drm/i915/gvt: make fb_decoder.h self-contained
>       drm/i915/gvt: make gtt.h self-contained
>       drm/i915/gvt: make interrupt.h self-contained
>       drm/i915/gvt: make mmio_context.h self-contained
>       drm/i915/gvt: make gvt.h self-contained
>       drm/i915/gvt: make scheduler.h self-contained
>       drm/i915/gvt: make mpt.h self-contained
> 
>  drivers/gpu/drm/i915/Makefile           | 10 +---------
>  drivers/gpu/drm/i915/gvt/execlist.h     |  3 ---
>  drivers/gpu/drm/i915/gvt/fb_decoder.h   |  6 ++++--
>  drivers/gpu/drm/i915/gvt/gtt.h          | 11 ++++++++++-
>  drivers/gpu/drm/i915/gvt/gvt.h          |  4 ++++
>  drivers/gpu/drm/i915/gvt/handlers.c     |  3 +--
>  drivers/gpu/drm/i915/gvt/interrupt.h    |  5 ++++-
>  drivers/gpu/drm/i915/gvt/mmio_context.h | 11 +++++++++++
>  drivers/gpu/drm/i915/gvt/mpt.h          |  2 ++
>  drivers/gpu/drm/i915/gvt/scheduler.h    |  5 +++++
>  10 files changed, 42 insertions(+), 18 deletions(-)
> 
> -- 
> 
> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827



> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx


-- 

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Jani Nikula]

On Tue, 05 Jan 2021, Zhenyu Wang <zhenyuw@linux.intel.com> 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, 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:
>> 
>>   drm/i915/gvt: treat intel_gvt_mpt as const in gvt code (2020-11-23 17:14:20 +0800)
>> 
>> are available in the Git repository at:
>> 
>>   https://github.com/intel/gvt-linux tags/gvt-next-fixes-2020-12-25
>> 
>> for you to fetch changes up to e056f669dbf76b8752b6cb0b8edd2f75cbdcabb1:
>> 
>>   drm/i915/gvt: make mpt.h self-contained (2020-12-22 11:41:35 +0800)
>> 
>> ----------------------------------------------------------------
>> gvt-next-fixes-2020-12-25
>> 
>> - Avoid one useless inline (Jani)
>> - make gvt header self-contained, fix CONFIG_DRM_I915_WERROR (Jani)
>> 
>> ----------------------------------------------------------------
>> Jani Nikula (9):
>>       drm/i915/gvt: avoid useless use of inline
>>       drm/i915/gvt: make execlist.h self-contained
>>       drm/i915/gvt: make fb_decoder.h self-contained
>>       drm/i915/gvt: make gtt.h self-contained
>>       drm/i915/gvt: make interrupt.h self-contained
>>       drm/i915/gvt: make mmio_context.h self-contained
>>       drm/i915/gvt: make gvt.h self-contained
>>       drm/i915/gvt: make scheduler.h self-contained
>>       drm/i915/gvt: make mpt.h self-contained
>> 
>>  drivers/gpu/drm/i915/Makefile           | 10 +---------
>>  drivers/gpu/drm/i915/gvt/execlist.h     |  3 ---
>>  drivers/gpu/drm/i915/gvt/fb_decoder.h   |  6 ++++--
>>  drivers/gpu/drm/i915/gvt/gtt.h          | 11 ++++++++++-
>>  drivers/gpu/drm/i915/gvt/gvt.h          |  4 ++++
>>  drivers/gpu/drm/i915/gvt/handlers.c     |  3 +--
>>  drivers/gpu/drm/i915/gvt/interrupt.h    |  5 ++++-
>>  drivers/gpu/drm/i915/gvt/mmio_context.h | 11 +++++++++++
>>  drivers/gpu/drm/i915/gvt/mpt.h          |  2 ++
>>  drivers/gpu/drm/i915/gvt/scheduler.h    |  5 +++++
>>  10 files changed, 42 insertions(+), 18 deletions(-)
>> 
>> -- 
>> 
>> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
>
>
>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Rodrigo Vivi]

On Tue, Jan 05, 2021 at 10:36:54AM +0200, Jani Nikula wrote:
> On Tue, 05 Jan 2021, Zhenyu Wang <zhenyuw@linux.intel.com> 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?

I believe drm-intel-next should be enough for this...

Pulled.

Thanks,
Rodrigo.

> 
> BR,
> Jani.
> 
> >
> > 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:
> >> 
> >>   drm/i915/gvt: treat intel_gvt_mpt as const in gvt code (2020-11-23 17:14:20 +0800)
> >> 
> >> are available in the Git repository at:
> >> 
> >>   https://github.com/intel/gvt-linux tags/gvt-next-fixes-2020-12-25
> >> 
> >> for you to fetch changes up to e056f669dbf76b8752b6cb0b8edd2f75cbdcabb1:
> >> 
> >>   drm/i915/gvt: make mpt.h self-contained (2020-12-22 11:41:35 +0800)
> >> 
> >> ----------------------------------------------------------------
> >> gvt-next-fixes-2020-12-25
> >> 
> >> - Avoid one useless inline (Jani)
> >> - make gvt header self-contained, fix CONFIG_DRM_I915_WERROR (Jani)
> >> 
> >> ----------------------------------------------------------------
> >> Jani Nikula (9):
> >>       drm/i915/gvt: avoid useless use of inline
> >>       drm/i915/gvt: make execlist.h self-contained
> >>       drm/i915/gvt: make fb_decoder.h self-contained
> >>       drm/i915/gvt: make gtt.h self-contained
> >>       drm/i915/gvt: make interrupt.h self-contained
> >>       drm/i915/gvt: make mmio_context.h self-contained
> >>       drm/i915/gvt: make gvt.h self-contained
> >>       drm/i915/gvt: make scheduler.h self-contained
> >>       drm/i915/gvt: make mpt.h self-contained
> >> 
> >>  drivers/gpu/drm/i915/Makefile           | 10 +---------
> >>  drivers/gpu/drm/i915/gvt/execlist.h     |  3 ---
> >>  drivers/gpu/drm/i915/gvt/fb_decoder.h   |  6 ++++--
> >>  drivers/gpu/drm/i915/gvt/gtt.h          | 11 ++++++++++-
> >>  drivers/gpu/drm/i915/gvt/gvt.h          |  4 ++++
> >>  drivers/gpu/drm/i915/gvt/handlers.c     |  3 +--
> >>  drivers/gpu/drm/i915/gvt/interrupt.h    |  5 ++++-
> >>  drivers/gpu/drm/i915/gvt/mmio_context.h | 11 +++++++++++
> >>  drivers/gpu/drm/i915/gvt/mpt.h          |  2 ++
> >>  drivers/gpu/drm/i915/gvt/scheduler.h    |  5 +++++
> >>  10 files changed, 42 insertions(+), 18 deletions(-)
> >> 
> >> -- 
> >> 
> >> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
> >
> >
> >
> >> _______________________________________________
> >> Intel-gfx mailing list
> >> Intel-gfx@lists.freedesktop.org
> >> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 
> -- 
> Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Zhenyu Wang]

[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]


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+ scalers (2023-04-24 14:48:42 +0300)

are available in the Git repository at:

  https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2023-04-28

for you to fetch changes up to 004040fdb55fa55463730c95d1384cb67f9396c3:

  drm/i915/gvt: Make use of idr_find and idr_for_each_entry in dmabuf (2023-04-28 15:21:17 +0800)

----------------------------------------------------------------
gvt-next-fixes-2023-04-28

- Use idr based dmabuf object reference (Cai Huoqing)

----------------------------------------------------------------
Cai Huoqing (1):
      drm/i915/gvt: Make use of idr_find and idr_for_each_entry in dmabuf

 drivers/gpu/drm/i915/gvt/dmabuf.c | 58 ++++++++-------------------------------
 drivers/gpu/drm/i915/gvt/dmabuf.h |  1 -
 drivers/gpu/drm/i915/gvt/gvt.h    |  1 -
 drivers/gpu/drm/i915/gvt/vgpu.c   |  1 -
 4 files changed, 12 insertions(+), 49 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

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

[Jani Nikula]

On Thu, 23 Feb 2023, Zhenyu Wang <zhenyuw@linux.intel.com> 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, pulled to drm-intel-next-fixes, and pushed out.

BR,
Jani.


>
> Thanks!
> --
> The following changes since commit 8038510b1fe443ffbc0e356db5f47cbb8678a594:
>
>   drm/i915: Fix system suspend without fbdev being initialized (2023-02-15 17:33:07 +0200)
>
> are available in the Git repository at:
>
>   https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2023-02-23
>
> for you to fetch changes up to 0b93efca3659f6d55ed31cff6722dca5f6e4d6e2:
>
>   drm/i915: move a Kconfig symbol to unbreak the menu presentation (2023-02-23 13:46:39 +0800)
>
> ----------------------------------------------------------------
> gvt-next-fixes-2023-02-23
>
> - use debugfs attribute for gvt debugfs entries (Deepak R Varma)
> - fix memory leak in vgpu destroy for debugfs_lookup() then remove (Greg KH)
> - fix DRM_I915_GVT kconfig symbol to unbreak menu presentation (Randy Dunlap)
> - fix typos (Deepak R Varma, Colin Ian King)
>
> ----------------------------------------------------------------
> Colin Ian King (1):
>       i915/gvt: Fix spelling mistake "vender" -> "vendor"
>
> Deepak R Varma (2):
>       drm/i915/gvt: Avoid full proxy f_ops for debugfs attributes
>       drm/i915/gvt: Remove extra semicolon
>
> Greg Kroah-Hartman (1):
>       i915: fix memory leak with using debugfs_lookup()
>
> Randy Dunlap (1):
>       drm/i915: move a Kconfig symbol to unbreak the menu presentation
>
>  drivers/gpu/drm/i915/Kconfig        |  6 +++---
>  drivers/gpu/drm/i915/gvt/debugfs.c  | 16 ++++++++--------
>  drivers/gpu/drm/i915/gvt/firmware.c |  2 +-
>  drivers/gpu/drm/i915/gvt/kvmgt.c    |  2 +-
>  drivers/gpu/drm/i915/gvt/vgpu.c     |  2 +-
>  5 files changed, 14 insertions(+), 14 deletions(-)

-- 
Jani Nikula, Intel Open Source Graphics Center

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

[Zhenyu Wang]

[-- Attachment #1: Type: text/plain, Size: 1803 bytes --]


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 8038510b1fe443ffbc0e356db5f47cbb8678a594:

  drm/i915: Fix system suspend without fbdev being initialized (2023-02-15 17:33:07 +0200)

are available in the Git repository at:

  https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2023-02-23

for you to fetch changes up to 0b93efca3659f6d55ed31cff6722dca5f6e4d6e2:

  drm/i915: move a Kconfig symbol to unbreak the menu presentation (2023-02-23 13:46:39 +0800)

----------------------------------------------------------------
gvt-next-fixes-2023-02-23

- use debugfs attribute for gvt debugfs entries (Deepak R Varma)
- fix memory leak in vgpu destroy for debugfs_lookup() then remove (Greg KH)
- fix DRM_I915_GVT kconfig symbol to unbreak menu presentation (Randy Dunlap)
- fix typos (Deepak R Varma, Colin Ian King)

----------------------------------------------------------------
Colin Ian King (1):
      i915/gvt: Fix spelling mistake "vender" -> "vendor"

Deepak R Varma (2):
      drm/i915/gvt: Avoid full proxy f_ops for debugfs attributes
      drm/i915/gvt: Remove extra semicolon

Greg Kroah-Hartman (1):
      i915: fix memory leak with using debugfs_lookup()

Randy Dunlap (1):
      drm/i915: move a Kconfig symbol to unbreak the menu presentation

 drivers/gpu/drm/i915/Kconfig        |  6 +++---
 drivers/gpu/drm/i915/gvt/debugfs.c  | 16 ++++++++--------
 drivers/gpu/drm/i915/gvt/firmware.c |  2 +-
 drivers/gpu/drm/i915/gvt/kvmgt.c    |  2 +-
 drivers/gpu/drm/i915/gvt/vgpu.c     |  2 +-
 5 files changed, 14 insertions(+), 14 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

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

[Jani Nikula]

On Thu, 29 Apr 2021, Zhenyu Wang <zhenyuw@linux.intel.com> 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 https://patchwork.freedesktop.org/series/89479/

Note that we can't pull anything from you that has a newer baseline than
what we have.

BR,
Jani.


>
> Thanks
> --
> The following changes since commit e65a4d378480101f222e8f6978c22e590c1fb7b5:
>
>   Merge tag 'gvt-next-fixes-2021-04-21' of https://github.com/intel/gvt-linux into drm-intel-next-fixes (2021-04-21 13:22:30 +0300)
>
> are available in the Git repository at:
>
>   https://github.com/intel/gvt-linux tags/gvt-next-fixes-2021-04-29
>
> for you to fetch changes up to d385c16173f28a18866abf54c764200c276dace0:
>
>   drm/i915/gvt: Prevent divided by zero when calculating refresh rate (2021-04-29 17:00:09 +0800)
>
> ----------------------------------------------------------------
> gvt-next-fixes-2021-04-29
>
> - Fix possible divide error in vgpu display rate calculation (Colin)
>
> ----------------------------------------------------------------
> Colin Xu (1):
>       drm/i915/gvt: Prevent divided by zero when calculating refresh rate
>
>  drivers/gpu/drm/i915/gvt/handlers.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Zhenyu Wang]

[-- Attachment #1.1: Type: text/plain, Size: 1173 bytes --]


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 commit e65a4d378480101f222e8f6978c22e590c1fb7b5:

  Merge tag 'gvt-next-fixes-2021-04-21' of https://github.com/intel/gvt-linux into drm-intel-next-fixes (2021-04-21 13:22:30 +0300)

are available in the Git repository at:

  https://github.com/intel/gvt-linux tags/gvt-next-fixes-2021-04-29

for you to fetch changes up to d385c16173f28a18866abf54c764200c276dace0:

  drm/i915/gvt: Prevent divided by zero when calculating refresh rate (2021-04-29 17:00:09 +0800)

----------------------------------------------------------------
gvt-next-fixes-2021-04-29

- Fix possible divide error in vgpu display rate calculation (Colin)

----------------------------------------------------------------
Colin Xu (1):
      drm/i915/gvt: Prevent divided by zero when calculating refresh rate

 drivers/gpu/drm/i915/gvt/handlers.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Jani Nikula]

On Wed, 21 Apr 2021, Zhenyu Wang <zhenyuw@linux.intel.com> 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.
> --
> The following changes since commit d153e8c156dafeb847fd655f416cf81c007e8706:
>
>   Merge tag 'drm-intel-next-fixes-2021-02-25' of git://anongit.freedesktop.org/drm/drm-intel into drm-next (2021-02-26 05:08:51 +1000)
>
> are available in the Git repository at:
>
>   https://github.com/intel/gvt-linux tags/gvt-next-fixes-2021-04-21
>
> for you to fetch changes up to 0349ec19c484ed40dbc725820673df4d94334e8c:
>
>   drm/i915/gvt: Remove duplicated register accessible check (2021-04-21 17:56:06 +0800)
>
> ----------------------------------------------------------------
> gvt-next-fixes-2021-04-21
>
> - Remove one unused function warning (Jiapeng)
> - Fix intel_gvt_init_device() return type (Dan)
> - Remove one duplicated register accessible check (Zhenyu)
>
> ----------------------------------------------------------------
> Dan Carpenter (1):
>       drm/i915/gvt: Fix error code in intel_gvt_init_device()
>
> Jiapeng Chong (1):
>       drm/i915/gvt: remove useless function
>
> Zhenyu Wang (1):
>       drm/i915/gvt: Remove duplicated register accessible check
>
>  drivers/gpu/drm/i915/gvt/cmd_parser.c | 5 -----
>  drivers/gpu/drm/i915/gvt/gtt.c        | 6 ------
>  drivers/gpu/drm/i915/gvt/gvt.c        | 8 ++++----
>  3 files changed, 4 insertions(+), 15 deletions(-)

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Zhenyu Wang]

[-- Attachment #1.1: Type: text/plain, Size: 1418 bytes --]


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 'drm-intel-next-fixes-2021-02-25' of git://anongit.freedesktop.org/drm/drm-intel into drm-next (2021-02-26 05:08:51 +1000)

are available in the Git repository at:

  https://github.com/intel/gvt-linux tags/gvt-next-fixes-2021-04-21

for you to fetch changes up to 0349ec19c484ed40dbc725820673df4d94334e8c:

  drm/i915/gvt: Remove duplicated register accessible check (2021-04-21 17:56:06 +0800)

----------------------------------------------------------------
gvt-next-fixes-2021-04-21

- Remove one unused function warning (Jiapeng)
- Fix intel_gvt_init_device() return type (Dan)
- Remove one duplicated register accessible check (Zhenyu)

----------------------------------------------------------------
Dan Carpenter (1):
      drm/i915/gvt: Fix error code in intel_gvt_init_device()

Jiapeng Chong (1):
      drm/i915/gvt: remove useless function

Zhenyu Wang (1):
      drm/i915/gvt: Remove duplicated register accessible check

 drivers/gpu/drm/i915/gvt/cmd_parser.c | 5 -----
 drivers/gpu/drm/i915/gvt/gtt.c        | 6 ------
 drivers/gpu/drm/i915/gvt/gvt.c        | 8 ++++----
 3 files changed, 4 insertions(+), 15 deletions(-)

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Rodrigo Vivi]

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 time.
pulled now.

Happy New Year!

> 
> Thanks!
> --
> The following changes since commit 81ce8f04aa96f7f6cae05770f68b5d15be91f5a2:
> 
>   drm/i915/gt: Correct surface base address for renderclear (2021-02-17 06:19:04 -0500)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux tags/gvt-next-fixes-2021-02-22
> 
> for you to fetch changes up to 67f1120381df022a7016f4acc8d4880da9a66c03:
> 
>   drm/i915/gvt: Introduce per object locking in GVT scheduler. (2021-02-22 16:42:14 +0800)
> 
> ----------------------------------------------------------------
> gvt-next-fixes-2021-02-22
> 
> - Fix to use i915 default state for cmd parser on all engines (Chris)
> - Purge dev_priv->gt (Chris)
> - Fix gvt object ww locking (Zhi)
> 
> ----------------------------------------------------------------
> Chris Wilson (2):
>       drm/i915/gvt: Parse default state to update reg whitelist
>       drm/i915/gvt: Purge dev_priv->gt
> 
> Zhi Wang (1):
>       drm/i915/gvt: Introduce per object locking in GVT scheduler.
> 
>  drivers/gpu/drm/i915/gvt/cmd_parser.c | 93 ++++++++---------------------------
>  drivers/gpu/drm/i915/gvt/execlist.c   |  8 ++-
>  drivers/gpu/drm/i915/gvt/scheduler.c  | 52 +++++++++++++++-----
>  3 files changed, 64 insertions(+), 89 deletions(-)



> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Zhenyu Wang]

[-- Attachment #1.1: Type: text/plain, Size: 1377 bytes --]


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 surface base address for renderclear (2021-02-17 06:19:04 -0500)

are available in the Git repository at:

  https://github.com/intel/gvt-linux tags/gvt-next-fixes-2021-02-22

for you to fetch changes up to 67f1120381df022a7016f4acc8d4880da9a66c03:

  drm/i915/gvt: Introduce per object locking in GVT scheduler. (2021-02-22 16:42:14 +0800)

----------------------------------------------------------------
gvt-next-fixes-2021-02-22

- Fix to use i915 default state for cmd parser on all engines (Chris)
- Purge dev_priv->gt (Chris)
- Fix gvt object ww locking (Zhi)

----------------------------------------------------------------
Chris Wilson (2):
      drm/i915/gvt: Parse default state to update reg whitelist
      drm/i915/gvt: Purge dev_priv->gt

Zhi Wang (1):
      drm/i915/gvt: Introduce per object locking in GVT scheduler.

 drivers/gpu/drm/i915/gvt/cmd_parser.c | 93 ++++++++---------------------------
 drivers/gpu/drm/i915/gvt/execlist.c   |  8 ++-
 drivers/gpu/drm/i915/gvt/scheduler.c  | 52 +++++++++++++++-----
 3 files changed, 64 insertions(+), 89 deletions(-)

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Jani Nikula]

On Wed, 05 Aug 2020, Zhenyu Wang <zhenyuw@linux.intel.com> 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 mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Zhenyu Wang]

[-- Attachment #1.1: Type: text/plain, Size: 1379 bytes --]


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 available in the Git repository at:

  https://github.com/intel/gvt-linux tags/gvt-next-fixes-2020-08-05

for you to fetch changes up to 9e7c0efadb86ddb58965561bbca638d44792d78f:

  drm/i915/gvt: Do not reset pv_notified when vGPU transit from D3->D0 (2020-07-29 14:18:32 +0800)

----------------------------------------------------------------
gvt-next-fixes-2020-08-05

- Fix guest suspend/resume low performance handling of shadow ppgtt (Colin)
- Fix PV notifier handling for guest suspend/resume (Colin)

----------------------------------------------------------------
Colin Xu (2):
      drm/i915/gvt: Do not destroy ppgtt_mm during vGPU D3->D0.
      drm/i915/gvt: Do not reset pv_notified when vGPU transit from D3->D0

 drivers/gpu/drm/i915/gvt/cfg_space.c | 24 ++++++++++++++++++++++++
 drivers/gpu/drm/i915/gvt/gtt.c       |  2 +-
 drivers/gpu/drm/i915/gvt/gtt.h       |  2 ++
 drivers/gpu/drm/i915/gvt/gvt.h       |  3 +++
 drivers/gpu/drm/i915/gvt/vgpu.c      | 20 +++++++++++++++++---
 5 files changed, 47 insertions(+), 4 deletions(-)


[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Joonas Lahtinen]

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 since commit 3a36aa237e4ed04553c0998cf5f47eda3e206e4f:
> 
>   drm/i915: Update DRIVER_DATE to 20200515 (2020-05-15 14:49:24 +0300)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux tags/gvt-next-fixes-2020-05-28
> 
> for you to fetch changes up to cb7ee52284a244fd14caec73df0d49e02891aac4:
> 
>   drm/i915/gvt: Use ARRAY_SIZE for vgpu_types (2020-05-19 17:18:50 +0800)
> 
> ----------------------------------------------------------------
> gvt-next-fixes-2020-05-28
> 
> - Fix one clang warning on debug only function (Nathan)
> - Use ARRAY_SIZE for coccicheck warn (Aishwarya)
> 
> ----------------------------------------------------------------
> Aishwarya Ramakrishnan (1):
>       drm/i915/gvt: Use ARRAY_SIZE for vgpu_types
> 
> Nathan Chancellor (1):
>       drm/i915: Mark check_shadow_context_ppgtt as maybe unused
> 
>  drivers/gpu/drm/i915/gvt/scheduler.c | 2 +-
>  drivers/gpu/drm/i915/gvt/vgpu.c      | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> 
> -- 
> Open Source Technology Center, Intel ltd.
> 
> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Zhenyu Wang]

[-- Attachment #1.1: Type: text/plain, Size: 1286 bytes --]


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 14:49:24 +0300)

are available in the Git repository at:

  https://github.com/intel/gvt-linux tags/gvt-next-fixes-2020-05-28

for you to fetch changes up to cb7ee52284a244fd14caec73df0d49e02891aac4:

  drm/i915/gvt: Use ARRAY_SIZE for vgpu_types (2020-05-19 17:18:50 +0800)

----------------------------------------------------------------
gvt-next-fixes-2020-05-28

- Fix one clang warning on debug only function (Nathan)
- Use ARRAY_SIZE for coccicheck warn (Aishwarya)

----------------------------------------------------------------
Aishwarya Ramakrishnan (1):
      drm/i915/gvt: Use ARRAY_SIZE for vgpu_types

Nathan Chancellor (1):
      drm/i915: Mark check_shadow_context_ppgtt as maybe unused

 drivers/gpu/drm/i915/gvt/scheduler.c | 2 +-
 drivers/gpu/drm/i915/gvt/vgpu.c      | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)


-- 
Open Source Technology Center, Intel ltd.

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Zhenyu Wang]

[-- Attachment #1.1: Type: text/plain, Size: 3271 bytes --]

On 2020.04.07 16:53:19 +0300, Jani Nikula wrote:
> On Tue, 07 Apr 2020, Rodrigo Vivi <rodrigo.vivi@intel.com> 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
> >> > > from KVM to use new VFIO dma r/w instead in this series: https://patchwork.freedesktop.org/series/72038/
> >> > > 
> >> > > As this depends on VFIO tree and looks VFIO pull for 5.7 is not settled down
> >> > > yet, we'd need to backmerge and send pull against vfio merge for 5.7.
> >> > 
> >> > I'm not sure if I'm following on which backmerge you are willing
> >> > us to do here. And for me it looks like late for 5.7 already.
> >> > 
> >> > Maybe you mean we ack all of this to go through vfio flow
> >> > then once that is settled drm backmerge and then drm-intel backmerge
> >> > and you backmerge...
> >> > 
> >> > Is that what you want?
> >> > 
> >> 
> >> My purpose is to get GVT side fixes of guest memory r/w through new
> >> vfio dma r/w interface in 5.7. As vfio 5.7-rc1 pull has already been
> >> merged in linus master, looks just want drm-intel backmerge now then
> >> could send gvt side fixes. Ok for you?
> >
> > I'm afraid it is too late for that. That would depend on backmerge
> > of drm itself as well... And we are in a point that we are about to
> > move from drm-next to drm-fixes.
> 
> *If* they're fixes, drm-intel-fixes rebases on v5.7-rc1 or -rc2, and if
> they can send a gvt fixes pull based on that, it could work out.
> 

yeah, that's also what I'm thinking about. Here's more background.

In gvt we need to access guest pages in some places, our current way
is to call KVM interface, but it turns out later that this interface
is supposed to be used by arch code only and what we should actually
depend on is using IOVA for guest page access instead of using guest
physical address by KVM. So we tried to add IOVA based guest r/w
support for VFIO and change gvt to use that. In that way they're real
fixes to me.

> >
> > Also looking to the patches itself they look more content for -next
> > than -fixes and our window with drm closed on -rc6

I understand that but the patches mostly for vfio interface hadn't been
finalized during rc6 window..

> >
> > So it looks to me that this will have to wait for the 5.8.
> >
> > One good suggestion I heard from Daniel for cases like this in the
> > future is the use of topic branches so things don't get spread into
> > multiple versions like this.
> >

Good idea. Does that mean such topic branch could be merged during
e.g -rc1 merge window?

Thanks

> >> 
> >> Sorry for late reply, I was out for a short vacation.
> >
> > Sorry for not been able to help further here
> >
> > Thanks,
> > Rodrigo.
> >
> >> 
> >> Thanks
> >> 
> >> -- 
> >> Open Source Technology Center, Intel ltd.
> >> 
> >> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
> >
> >
> 
> -- 
> Jani Nikula, Intel Open Source Graphics Center

-- 
Open Source Technology Center, Intel ltd.

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Jani Nikula]

On Tue, 07 Apr 2020, Rodrigo Vivi <rodrigo.vivi@intel.com> 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
>> > > from KVM to use new VFIO dma r/w instead in this series: https://patchwork.freedesktop.org/series/72038/
>> > > 
>> > > As this depends on VFIO tree and looks VFIO pull for 5.7 is not settled down
>> > > yet, we'd need to backmerge and send pull against vfio merge for 5.7.
>> > 
>> > I'm not sure if I'm following on which backmerge you are willing
>> > us to do here. And for me it looks like late for 5.7 already.
>> > 
>> > Maybe you mean we ack all of this to go through vfio flow
>> > then once that is settled drm backmerge and then drm-intel backmerge
>> > and you backmerge...
>> > 
>> > Is that what you want?
>> > 
>> 
>> My purpose is to get GVT side fixes of guest memory r/w through new
>> vfio dma r/w interface in 5.7. As vfio 5.7-rc1 pull has already been
>> merged in linus master, looks just want drm-intel backmerge now then
>> could send gvt side fixes. Ok for you?
>
> I'm afraid it is too late for that. That would depend on backmerge
> of drm itself as well... And we are in a point that we are about to
> move from drm-next to drm-fixes.

*If* they're fixes, drm-intel-fixes rebases on v5.7-rc1 or -rc2, and if
they can send a gvt fixes pull based on that, it could work out.

BR,
Jani.


>
> Also looking to the patches itself they look more content for -next
> than -fixes and our window with drm closed on -rc6
>
> So it looks to me that this will have to wait for the 5.8.
>
> One good suggestion I heard from Daniel for cases like this in the
> future is the use of topic branches so things don't get spread into
> multiple versions like this.
>
>> 
>> Sorry for late reply, I was out for a short vacation.
>
> Sorry for not been able to help further here
>
> Thanks,
> Rodrigo.
>
>> 
>> Thanks
>> 
>> -- 
>> Open Source Technology Center, Intel ltd.
>> 
>> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
>
>

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Rodrigo Vivi]

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: https://patchwork.freedesktop.org/series/72038/
> > > 
> > > As this depends on VFIO tree and looks VFIO pull for 5.7 is not settled down
> > > yet, we'd need to backmerge and send pull against vfio merge for 5.7.
> > 
> > I'm not sure if I'm following on which backmerge you are willing
> > us to do here. And for me it looks like late for 5.7 already.
> > 
> > Maybe you mean we ack all of this to go through vfio flow
> > then once that is settled drm backmerge and then drm-intel backmerge
> > and you backmerge...
> > 
> > Is that what you want?
> > 
> 
> My purpose is to get GVT side fixes of guest memory r/w through new
> vfio dma r/w interface in 5.7. As vfio 5.7-rc1 pull has already been
> merged in linus master, looks just want drm-intel backmerge now then
> could send gvt side fixes. Ok for you?

I'm afraid it is too late for that. That would depend on backmerge
of drm itself as well... And we are in a point that we are about to
move from drm-next to drm-fixes.

Also looking to the patches itself they look more content for -next
than -fixes and our window with drm closed on -rc6

So it looks to me that this will have to wait for the 5.8.

One good suggestion I heard from Daniel for cases like this in the
future is the use of topic branches so things don't get spread into
multiple versions like this.

> 
> Sorry for late reply, I was out for a short vacation.

Sorry for not been able to help further here

Thanks,
Rodrigo.

> 
> Thanks
> 
> -- 
> Open Source Technology Center, Intel ltd.
> 
> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827


_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Zhenyu Wang]

[-- Attachment #1.1: Type: text/plain, Size: 1196 bytes --]

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 on VFIO tree and looks VFIO pull for 5.7 is not settled down
> > yet, we'd need to backmerge and send pull against vfio merge for 5.7.
> 
> I'm not sure if I'm following on which backmerge you are willing
> us to do here. And for me it looks like late for 5.7 already.
> 
> Maybe you mean we ack all of this to go through vfio flow
> then once that is settled drm backmerge and then drm-intel backmerge
> and you backmerge...
> 
> Is that what you want?
> 

My purpose is to get GVT side fixes of guest memory r/w through new
vfio dma r/w interface in 5.7. As vfio 5.7-rc1 pull has already been
merged in linus master, looks just want drm-intel backmerge now then
could send gvt side fixes. Ok for you?

Sorry for late reply, I was out for a short vacation.

Thanks

-- 
Open Source Technology Center, Intel ltd.

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Rodrigo Vivi]

+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.
> > > 
> > > 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:
> > > 
> > >   https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2020-03-31
> > > 
> > > for you to fetch changes up to eb0ff8074e0baecba2cd0c7813f6cfa99bafc430:
> > > 
> > >   drm/i915/gvt: Fix klocwork issues about data size (2020-03-27 15:37:58 +0800)
> > 
> > pulled, thanks
> 
> 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 on VFIO tree and looks VFIO pull for 5.7 is not settled down
> yet, we'd need to backmerge and send pull against vfio merge for 5.7.

I'm not sure if I'm following on which backmerge you are willing
us to do here. And for me it looks like late for 5.7 already.

Maybe you mean we ack all of this to go through vfio flow
then once that is settled drm backmerge and then drm-intel backmerge
and you backmerge...

Is that what you want?

> 
> thanks
> 
> > 
> > > 
> > > ----------------------------------------------------------------
> > > gvt-next-fixes-2020-03-31
> > > 
> > > - Fix non-privilege access warning (Tina)
> > > - Fix display port type (Tina)
> > > - BDW cmd parser missed SWTESS_BASE_ADDRESS (Yan)
> > > - Bypass length check of LRI (Yan)
> > > - Fix one klocwork warning (Tina)
> > > 
> > > ----------------------------------------------------------------
> > > Tina Zhang (3):
> > >       drm/i915/gvt: Add some regs to force-to-nonpriv whitelist
> > >       drm/i915/gvt: Fix display port type issue
> > >       drm/i915/gvt: Fix klocwork issues about data size
> > > 
> > > Yan Zhao (2):
> > >       drm/i915/gvt: add support to command SWTESS_BASE_ADDRESS
> > >       drm/i915/gvt: do not check len & max_len for lri
> > > 
> > >  drivers/gpu/drm/i915/gvt/cmd_parser.c | 16 ++++------------
> > >  drivers/gpu/drm/i915/gvt/display.c    |  6 +++---
> > >  drivers/gpu/drm/i915/gvt/handlers.c   |  8 ++++++--
> > >  drivers/gpu/drm/i915/gvt/scheduler.c  |  4 ++--
> > >  4 files changed, 15 insertions(+), 19 deletions(-)
> > > 
> > > -- 
> > > Open Source Technology Center, Intel ltd.
> > > 
> > > $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
> > 
> > 
> > _______________________________________________
> > intel-gvt-dev mailing list
> > intel-gvt-dev@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev
> 
> -- 
> Open Source Technology Center, Intel ltd.
> 
> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827



> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Zhenyu Wang]

[-- Attachment #1.1: Type: text/plain, Size: 2564 bytes --]

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 a61ac1e75105a077ec1efd6923ae3c619f862304:
> > 
> >   drm/i915/gvt: Wean gvt off using dev_priv (2020-03-06 10:08:10 +0800)
> > 
> > are available in the Git repository at:
> > 
> >   https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2020-03-31
> > 
> > for you to fetch changes up to eb0ff8074e0baecba2cd0c7813f6cfa99bafc430:
> > 
> >   drm/i915/gvt: Fix klocwork issues about data size (2020-03-27 15:37:58 +0800)
> 
> pulled, thanks

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 on VFIO tree and looks VFIO pull for 5.7 is not settled down
yet, we'd need to backmerge and send pull against vfio merge for 5.7.

thanks

> 
> > 
> > ----------------------------------------------------------------
> > gvt-next-fixes-2020-03-31
> > 
> > - Fix non-privilege access warning (Tina)
> > - Fix display port type (Tina)
> > - BDW cmd parser missed SWTESS_BASE_ADDRESS (Yan)
> > - Bypass length check of LRI (Yan)
> > - Fix one klocwork warning (Tina)
> > 
> > ----------------------------------------------------------------
> > Tina Zhang (3):
> >       drm/i915/gvt: Add some regs to force-to-nonpriv whitelist
> >       drm/i915/gvt: Fix display port type issue
> >       drm/i915/gvt: Fix klocwork issues about data size
> > 
> > Yan Zhao (2):
> >       drm/i915/gvt: add support to command SWTESS_BASE_ADDRESS
> >       drm/i915/gvt: do not check len & max_len for lri
> > 
> >  drivers/gpu/drm/i915/gvt/cmd_parser.c | 16 ++++------------
> >  drivers/gpu/drm/i915/gvt/display.c    |  6 +++---
> >  drivers/gpu/drm/i915/gvt/handlers.c   |  8 ++++++--
> >  drivers/gpu/drm/i915/gvt/scheduler.c  |  4 ++--
> >  4 files changed, 15 insertions(+), 19 deletions(-)
> > 
> > -- 
> > Open Source Technology Center, Intel ltd.
> > 
> > $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
> 
> 
> _______________________________________________
> intel-gvt-dev mailing list
> intel-gvt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev

-- 
Open Source Technology Center, Intel ltd.

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Rodrigo Vivi]

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 10:08:10 +0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2020-03-31
> 
> for you to fetch changes up to eb0ff8074e0baecba2cd0c7813f6cfa99bafc430:
> 
>   drm/i915/gvt: Fix klocwork issues about data size (2020-03-27 15:37:58 +0800)

pulled, thanks

> 
> ----------------------------------------------------------------
> gvt-next-fixes-2020-03-31
> 
> - Fix non-privilege access warning (Tina)
> - Fix display port type (Tina)
> - BDW cmd parser missed SWTESS_BASE_ADDRESS (Yan)
> - Bypass length check of LRI (Yan)
> - Fix one klocwork warning (Tina)
> 
> ----------------------------------------------------------------
> Tina Zhang (3):
>       drm/i915/gvt: Add some regs to force-to-nonpriv whitelist
>       drm/i915/gvt: Fix display port type issue
>       drm/i915/gvt: Fix klocwork issues about data size
> 
> Yan Zhao (2):
>       drm/i915/gvt: add support to command SWTESS_BASE_ADDRESS
>       drm/i915/gvt: do not check len & max_len for lri
> 
>  drivers/gpu/drm/i915/gvt/cmd_parser.c | 16 ++++------------
>  drivers/gpu/drm/i915/gvt/display.c    |  6 +++---
>  drivers/gpu/drm/i915/gvt/handlers.c   |  8 ++++++--
>  drivers/gpu/drm/i915/gvt/scheduler.c  |  4 ++--
>  4 files changed, 15 insertions(+), 19 deletions(-)
> 
> -- 
> Open Source Technology Center, Intel ltd.
> 
> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827


_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Zhenyu Wang]

[-- Attachment #1.1: Type: text/plain, Size: 1585 bytes --]


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:

  https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2020-03-31

for you to fetch changes up to eb0ff8074e0baecba2cd0c7813f6cfa99bafc430:

  drm/i915/gvt: Fix klocwork issues about data size (2020-03-27 15:37:58 +0800)

----------------------------------------------------------------
gvt-next-fixes-2020-03-31

- Fix non-privilege access warning (Tina)
- Fix display port type (Tina)
- BDW cmd parser missed SWTESS_BASE_ADDRESS (Yan)
- Bypass length check of LRI (Yan)
- Fix one klocwork warning (Tina)

----------------------------------------------------------------
Tina Zhang (3):
      drm/i915/gvt: Add some regs to force-to-nonpriv whitelist
      drm/i915/gvt: Fix display port type issue
      drm/i915/gvt: Fix klocwork issues about data size

Yan Zhao (2):
      drm/i915/gvt: add support to command SWTESS_BASE_ADDRESS
      drm/i915/gvt: do not check len & max_len for lri

 drivers/gpu/drm/i915/gvt/cmd_parser.c | 16 ++++------------
 drivers/gpu/drm/i915/gvt/display.c    |  6 +++---
 drivers/gpu/drm/i915/gvt/handlers.c   |  8 ++++++--
 drivers/gpu/drm/i915/gvt/scheduler.c  |  4 ++--
 4 files changed, 15 insertions(+), 19 deletions(-)

-- 
Open Source Technology Center, Intel ltd.

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Zhenyu Wang]

[-- Attachment #1.1: Type: text/plain, Size: 562 bytes --]

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: and Link: tags to the GVT
> commits?
> 

For Fixes: we've already been caution to add when needed, I'll try to
handle Link: tag later.

Thanks

-- 
Open Source Technology Center, Intel ltd.

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Joonas Lahtinen]

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
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Zhenyu Wang]

[-- Attachment #1.1: Type: text/plain, Size: 1791 bytes --]


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:
> 
>   drm/i915/gvt: Stop initializing pvinfo through reading mmio (2019-11-08 11:08:07 +0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux tags/gvt-next-fixes-2019-12-02
> 
> for you to fetch changes up to 92b1aa773fadb4e2a90ed5d3beecb422d568ad9a:
> 
>   drm/i915/gvt: Fix cmd length check for MI_ATOMIC (2019-12-02 11:06:49 +0800)
> 
> ----------------------------------------------------------------
> gvt-next-fixes-2019-12-02
> 
> - Fix cmd parser for MI_ATOMIC (Zhenyu)
> - Fix non-priv register access warning on CFL (Fred)
> 
> ----------------------------------------------------------------
> Gao, Fred (2):
>       drm/i915/gvt: Refine non privilege register address calucation
>       drm/i915/gvt: Update force-to-nonpriv register whitelist
> 
> Zhenyu Wang (1):
>       drm/i915/gvt: Fix cmd length check for MI_ATOMIC
> 
>  drivers/gpu/drm/i915/gvt/cmd_parser.c | 6 +++---
>  drivers/gpu/drm/i915/gvt/handlers.c   | 5 +++--
>  2 files changed, 6 insertions(+), 5 deletions(-)
> 
> 
> -- 
> Open Source Technology Center, Intel ltd.
> 
> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827



> _______________________________________________
> intel-gvt-dev mailing list
> intel-gvt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev


-- 
Open Source Technology Center, Intel ltd.

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Zhenyu Wang]

[-- Attachment #1.1: Type: text/plain, Size: 1344 bytes --]


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 11:08:07 +0800)

are available in the Git repository at:

  https://github.com/intel/gvt-linux tags/gvt-next-fixes-2019-12-02

for you to fetch changes up to 92b1aa773fadb4e2a90ed5d3beecb422d568ad9a:

  drm/i915/gvt: Fix cmd length check for MI_ATOMIC (2019-12-02 11:06:49 +0800)

----------------------------------------------------------------
gvt-next-fixes-2019-12-02

- Fix cmd parser for MI_ATOMIC (Zhenyu)
- Fix non-priv register access warning on CFL (Fred)

----------------------------------------------------------------
Gao, Fred (2):
      drm/i915/gvt: Refine non privilege register address calucation
      drm/i915/gvt: Update force-to-nonpriv register whitelist

Zhenyu Wang (1):
      drm/i915/gvt: Fix cmd length check for MI_ATOMIC

 drivers/gpu/drm/i915/gvt/cmd_parser.c | 6 +++---
 drivers/gpu/drm/i915/gvt/handlers.c   | 5 +++--
 2 files changed, 6 insertions(+), 5 deletions(-)


-- 
Open Source Technology Center, Intel ltd.

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Joonas Lahtinen]

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
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Zhenyu Wang]

[-- Attachment #1.1: Type: text/plain, Size: 1051 bytes --]


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 repository at:

  https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2019-11-12

for you to fetch changes up to 83faaf074e6d1ca4d1441aded0d3f01bce413479:

  drm/i915/gvt: Stop initializing pvinfo through reading mmio (2019-11-08 11:08:07 +0800)

----------------------------------------------------------------
gvt-next-fixes-2019-11-12

- Remove PVINFO read for initial state (Tina)

----------------------------------------------------------------
Tina Zhang (1):
      drm/i915/gvt: Stop initializing pvinfo through reading mmio

 drivers/gpu/drm/i915/gvt/handlers.c | 4 ++++
 1 file changed, 4 insertions(+)


-- 
Open Source Technology Center, Intel ltd.

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx