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

[Jani Nikula]

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, 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

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

[Rodrigo Vivi]

On Thu, Nov 17, 2022 at 02:41:06PM +0800, Zhenyu Wang wrote:
> On 2022.11.17 03:37:17 +, Vivi, Rodrigo wrote:
> > On Thu, 2022-11-17 at 11:02 +0800, Zhenyu Wang wrote:
> > > On 2022.11.15 10:36:59 -0500, Rodrigo Vivi wrote:
> > > > On Fri, Nov 11, 2022 at 04:59:03PM +0800, Zhenyu Wang wrote:
> > > > > Hi,
> > > > > 
> > > > > Here's current accumulated changes in gvt-next. Sorry that I
> > > > > delayed
> > > > > to refresh them on time for upstream...It contains mostly kernel
> > > > > doc,
> > > > > typo fixes and small code cleanups, as details below.
> > > > > 
> > > > > btw, one gvt change for next
> > > > > https://patchwork.freedesktop.org/patch/58/
> > > > > is still pending, I need a backmerge from linus tree e.g with
> > > > > recent vfio/mdev
> > > > > consolidate change with gvt and Jason's fix for destroy device,
> > > > > to apply Zhi's
> > > > > change cleanly. Pls help on that.
> > > > > 
> 
> > 
> > Based on what I could verify the commiter signature is really not
> > there. It looks like you later forced a rebase and while
> > rebasing you forgot to re-sign everything.
> > 
> 
> Hi, pls re-pull this one.

This one worked out. Pulled, thanks!

> 
> thanks!
> ---
> The following changes since commit a6ebd538364b1e9e6048faaafbc0188172ed50c3:
> 
>   drm/i915/sdvo: Fix debug print (2022-10-28 14:46:21 +0300)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-2022-11-17
> 
> for you to fetch changes up to 04ec334e1a0381c3305da4d277cef9250769ca43:
> 
>   drm/i915/gvt: Remove the unused function get_pt_type() (2022-11-17 14:07:09 
> +0800)
> 
> 
> gvt-next-2022-11-17
> 
> - kernel doc fixes
> - remove vgpu->released sanity check
> - small clean up
> 
> 
> Colin Ian King (1):
>   drm/i915/reg: Fix spelling mistake "Unsupport" -> "Unsupported"
> 
> Jiapeng Chong (4):
>   drm/i915/gvt: Fix kernel-doc
>   drm/i915/gvt: Fix kernel-doc
>   drm/i915/gvt: Fix kernel-doc
>   drm/i915/gvt: Remove the unused function get_pt_type()
> 
> Julia Lawall (1):
>   drm/i915/gvt: fix typo in comment
> 
> Mauro Carvalho Chehab (1):
>   drm/i915: gvt: fix kernel-doc trivial warnings
> 
> Paulo Miguel Almeida (1):
>   i915/gvt: remove hardcoded value on crc32_start calculation
> 
> Zhi Wang (1):
>   drm/i915/gvt: remove the vgpu->released and its sanity check
> 
> wangjianli (1):
>   drm/i915: fix repeated words in comments
> 
>  drivers/gpu/drm/i915/gvt/aperture_gm.c  | 4 ++--
>  drivers/gpu/drm/i915/gvt/cfg_space.c| 2 +-
>  drivers/gpu/drm/i915/gvt/dmabuf.h   | 2 +-
>  drivers/gpu/drm/i915/gvt/firmware.c | 2 +-
>  drivers/gpu/drm/i915/gvt/gtt.c  | 9 ++---
>  drivers/gpu/drm/i915/gvt/gvt.h  | 2 --
>  drivers/gpu/drm/i915/gvt/handlers.c | 4 ++--
>  drivers/gpu/drm/i915/gvt/kvmgt.c| 4 
>  drivers/gpu/drm/i915/gvt/mmio_context.c | 2 +-
>  drivers/gpu/drm/i915/gvt/page_track.c   | 2 +-
>  drivers/gpu/drm/i915/gvt/vgpu.c | 6 +++---
>  11 files changed, 14 insertions(+), 25 deletions(-)

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

[Zhenyu Wang]

On 2022.11.17 03:37:17 +, Vivi, Rodrigo wrote:
> On Thu, 2022-11-17 at 11:02 +0800, Zhenyu Wang wrote:
> > On 2022.11.15 10:36:59 -0500, Rodrigo Vivi wrote:
> > > On Fri, Nov 11, 2022 at 04:59:03PM +0800, Zhenyu Wang wrote:
> > > > Hi,
> > > > 
> > > > Here's current accumulated changes in gvt-next. Sorry that I
> > > > delayed
> > > > to refresh them on time for upstream...It contains mostly kernel
> > > > doc,
> > > > typo fixes and small code cleanups, as details below.
> > > > 
> > > > btw, one gvt change for next
> > > > https://patchwork.freedesktop.org/patch/58/
> > > > is still pending, I need a backmerge from linus tree e.g with
> > > > recent vfio/mdev
> > > > consolidate change with gvt and Jason's fix for destroy device,
> > > > to apply Zhi's
> > > > change cleanly. Pls help on that.
> > > > 

> 
> Based on what I could verify the commiter signature is really not
> there. It looks like you later forced a rebase and while
> rebasing you forgot to re-sign everything.
> 

Hi, pls re-pull this one.

thanks!
---
The following changes since commit a6ebd538364b1e9e6048faaafbc0188172ed50c3:

  drm/i915/sdvo: Fix debug print (2022-10-28 14:46:21 +0300)

are available in the Git repository at:

  https://github.com/intel/gvt-linux.git tags/gvt-next-2022-11-17

for you to fetch changes up to 04ec334e1a0381c3305da4d277cef9250769ca43:

  drm/i915/gvt: Remove the unused function get_pt_type() (2022-11-17 14:07:09 
+0800)


gvt-next-2022-11-17

- kernel doc fixes
- remove vgpu->released sanity check
- small clean up


Colin Ian King (1):
  drm/i915/reg: Fix spelling mistake "Unsupport" -> "Unsupported"

Jiapeng Chong (4):
  drm/i915/gvt: Fix kernel-doc
  drm/i915/gvt: Fix kernel-doc
  drm/i915/gvt: Fix kernel-doc
  drm/i915/gvt: Remove the unused function get_pt_type()

Julia Lawall (1):
  drm/i915/gvt: fix typo in comment

Mauro Carvalho Chehab (1):
  drm/i915: gvt: fix kernel-doc trivial warnings

Paulo Miguel Almeida (1):
  i915/gvt: remove hardcoded value on crc32_start calculation

Zhi Wang (1):
  drm/i915/gvt: remove the vgpu->released and its sanity check

wangjianli (1):
  drm/i915: fix repeated words in comments

 drivers/gpu/drm/i915/gvt/aperture_gm.c  | 4 ++--
 drivers/gpu/drm/i915/gvt/cfg_space.c| 2 +-
 drivers/gpu/drm/i915/gvt/dmabuf.h   | 2 +-
 drivers/gpu/drm/i915/gvt/firmware.c | 2 +-
 drivers/gpu/drm/i915/gvt/gtt.c  | 9 ++---
 drivers/gpu/drm/i915/gvt/gvt.h  | 2 --
 drivers/gpu/drm/i915/gvt/handlers.c | 4 ++--
 drivers/gpu/drm/i915/gvt/kvmgt.c| 4 
 drivers/gpu/drm/i915/gvt/mmio_context.c | 2 +-
 drivers/gpu/drm/i915/gvt/page_track.c   | 2 +-
 drivers/gpu/drm/i915/gvt/vgpu.c | 6 +++---
 11 files changed, 14 insertions(+), 25 deletions(-)


signature.asc
Description: PGP signature

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

[Zhenyu Wang]

On 2022.11.17 03:37:17 +, Vivi, Rodrigo wrote:
> On Thu, 2022-11-17 at 11:02 +0800, Zhenyu Wang wrote:
> > On 2022.11.15 10:36:59 -0500, Rodrigo Vivi wrote:
> > > On Fri, Nov 11, 2022 at 04:59:03PM +0800, Zhenyu Wang wrote:
> > > > Hi,
> > > > 
> > > > Here's current accumulated changes in gvt-next. Sorry that I
> > > > delayed
> > > > to refresh them on time for upstream...It contains mostly kernel
> > > > doc,
> > > > typo fixes and small code cleanups, as details below.
> > > > 
> > > > btw, one gvt change for next
> > > > https://patchwork.freedesktop.org/patch/58/
> > > > is still pending, I need a backmerge from linus tree e.g with
> > > > recent vfio/mdev
> > > > consolidate change with gvt and Jason's fix for destroy device,
> > > > to apply Zhi's
> > > > change cleanly. Pls help on that.
> > > > 
> > > > Thanks!
> > > > ---
> > > > The following changes since commit
> > > > a6ebd538364b1e9e6048faaafbc0188172ed50c3:
> > > > 
> > > > ?? drm/i915/sdvo: Fix debug print (2022-10-28 14:46:21 +0300)
> > > > 
> > > > are available in the Git repository at:
> > > > 
> > > > ?? https://github.com/intel/gvt-linux.git??tags/gvt-next-2022-11-11
> > > > 
> > > > for you to fetch changes up to
> > > > 50468ca2e2e1ce882f060a8c263f678affe112db:
> > > > 
> > > > ?? drm/i915/gvt: Remove the unused function get_pt_type() (2022-
> > > > 11-08 15:34:06 +0800)
> > > > 
> > > > 
> > > > gvt-next-2022-11-11
> > > > 
> > > > - kernel doc fixes
> > > > - remove vgpu->released sanity check
> > > > - small clean up
> > > > 
> > > > 
> > > > Colin Ian King (1):
> > > > ?? drm/i915/reg: Fix spelling mistake "Unsupport" ->
> > > > "Unsupported"
> > > 
> > > dim: d7e4e9579f01 ("drm/i915/reg: Fix spelling mistake "Unsupport"
> > > -> "Unsupported""): committer Signed-off-by missing.
> > > 
> > > could you please fix this before we can merge this pr?
> > > 
> > 
> > That should still be .mailmap issue for Colin's email...
> > But could we improve our dim script to grep mailmap in that case? So
> > if s-o-b mail is valid
> > in mailmap, we should still allow it, right?
> 
> Based on what I could verify the commiter signature is really not
> there. It looks like you later forced a rebase and while
> rebasing you forgot to re-sign everything.
>

Oops! Sorry for that. I'll redo this.

> We need to fix this in your tree to avoid propagating that to other
> trees later:
> 
> From tig view:
> Commit: Zhenyu Wang 
> CommitDate: Tue Nov 8 15:04:53 2022 +0800
> 
> drm/i915/reg: Fix spelling mistake "Unsupport" -> "Unsupported"
> 
> There is a spelling mistake in a gvt_vgpu_err error message. Fix
> it.
> 
> Fixes: 695fbc08d80f ("drm/i915/gvt: replace the gvt_err with
> gvt_vgpu_err")
> Signed-off-by: Colin Ian King 
> Signed-off-by: Zhi Wang 
> Link:
> http://patchwork.freedesktop.org/patch/msgid/20220315202449.2952845-1-colin.i.k...@gmail.com
> Reviewed-by: Zhi Wang 
> 
> no signature from you.
> 
> > 
> > > > 
> > > > Jiapeng Chong (4):
> > > > ?? drm/i915/gvt: Fix kernel-doc
> > > > ?? drm/i915/gvt: Fix kernel-doc
> > > > ?? drm/i915/gvt: Fix kernel-doc
> > > > ?? drm/i915/gvt: Remove the unused function get_pt_type()
> > > > 
> > > > Julia Lawall (1):
> > > > ?? drm/i915/gvt: fix typo in comment
> > > > 
> > > > Mauro Carvalho Chehab (1):
> > > > ?? drm/i915: gvt: fix kernel-doc trivial warnings
> > > > 
> > > > Paulo Miguel Almeida (1):
> > > > ?? i915/gvt: remove hardcoded value on crc32_start calculation
> > > > 
> > > > Zhi Wang (1):
> > > > ?? drm/i915/gvt: remove the vgpu->released and its sanity
> > > > check
> > > > 
> > > > wangjianli (1):
> > > > ?? drm/i915: fix repeated words in comments
> > > > 
> > > > ??drivers/gpu/drm/i915/gvt/aperture_gm.c?? | 4 ++--
> > > > ??drivers/gpu/drm/i915/gvt/cfg_space.c?? | 2 +-
> > > > ??drivers/gpu/drm/i915/gvt/dmabuf.h | 2 +-
> > > > ??drivers/gpu/drm/i915/gvt/firmware.c | 2 +-
> > > > ??drivers/gpu/drm/i915/gvt/gtt.c?? | 9 ++---
> > > > ??drivers/gpu/drm/i915/gvt/gvt.h?? | 2 --
> > > > ??drivers/gpu/drm/i915/gvt/handlers.c | 4 ++--
> > > > ??drivers/gpu/drm/i915/gvt/kvmgt.c?? | 4 
> > > > ??drivers/gpu/drm/i915/gvt/mmio_context.c | 2 +-
> > > > ??drivers/gpu/drm/i915/gvt/page_track.c | 2 +-
> > > > ??drivers/gpu/drm/i915/gvt/vgpu.c | 6 +++---
> > > > ??11 files changed, 14 insertions(+), 25 deletions(-)
> > > 
> > > 
> 


signature.asc
Description: PGP signature

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

[Vivi, Rodrigo]

On Thu, 2022-11-17 at 11:02 +0800, Zhenyu Wang wrote:
> On 2022.11.15 10:36:59 -0500, Rodrigo Vivi wrote:
> > On Fri, Nov 11, 2022 at 04:59:03PM +0800, Zhenyu Wang wrote:
> > > Hi,
> > > 
> > > Here's current accumulated changes in gvt-next. Sorry that I
> > > delayed
> > > to refresh them on time for upstream...It contains mostly kernel
> > > doc,
> > > typo fixes and small code cleanups, as details below.
> > > 
> > > btw, one gvt change for next
> > > https://patchwork.freedesktop.org/patch/58/
> > > is still pending, I need a backmerge from linus tree e.g with
> > > recent vfio/mdev
> > > consolidate change with gvt and Jason's fix for destroy device,
> > > to apply Zhi's
> > > change cleanly. Pls help on that.
> > > 
> > > Thanks!
> > > ---
> > > The following changes since commit
> > > a6ebd538364b1e9e6048faaafbc0188172ed50c3:
> > > 
> > >   drm/i915/sdvo: Fix debug print (2022-10-28 14:46:21 +0300)
> > > 
> > > are available in the Git repository at:
> > > 
> > >   https://github.com/intel/gvt-linux.git tags/gvt-next-2022-11-11
> > > 
> > > for you to fetch changes up to
> > > 50468ca2e2e1ce882f060a8c263f678affe112db:
> > > 
> > >   drm/i915/gvt: Remove the unused function get_pt_type() (2022-
> > > 11-08 15:34:06 +0800)
> > > 
> > > 
> > > gvt-next-2022-11-11
> > > 
> > > - kernel doc fixes
> > > - remove vgpu->released sanity check
> > > - small clean up
> > > 
> > > 
> > > Colin Ian King (1):
> > >   drm/i915/reg: Fix spelling mistake "Unsupport" ->
> > > "Unsupported"
> > 
> > dim: d7e4e9579f01 ("drm/i915/reg: Fix spelling mistake "Unsupport"
> > -> "Unsupported""): committer Signed-off-by missing.
> > 
> > could you please fix this before we can merge this pr?
> > 
> 
> That should still be .mailmap issue for Colin's email...
> But could we improve our dim script to grep mailmap in that case? So
> if s-o-b mail is valid
> in mailmap, we should still allow it, right?

Based on what I could verify the commiter signature is really not
there. It looks like you later forced a rebase and while
rebasing you forgot to re-sign everything.

We need to fix this in your tree to avoid propagating that to other
trees later:

From tig view:
Commit: Zhenyu Wang 
CommitDate: Tue Nov 8 15:04:53 2022 +0800

drm/i915/reg: Fix spelling mistake "Unsupport" -> "Unsupported"

There is a spelling mistake in a gvt_vgpu_err error message. Fix
it.

Fixes: 695fbc08d80f ("drm/i915/gvt: replace the gvt_err with
gvt_vgpu_err")
Signed-off-by: Colin Ian King 
Signed-off-by: Zhi Wang 
Link:
http://patchwork.freedesktop.org/patch/msgid/20220315202449.2952845-1-colin.i.k...@gmail.com
Reviewed-by: Zhi Wang 

no signature from you.

> 
> > > 
> > > Jiapeng Chong (4):
> > >   drm/i915/gvt: Fix kernel-doc
> > >   drm/i915/gvt: Fix kernel-doc
> > >   drm/i915/gvt: Fix kernel-doc
> > >   drm/i915/gvt: Remove the unused function get_pt_type()
> > > 
> > > Julia Lawall (1):
> > >   drm/i915/gvt: fix typo in comment
> > > 
> > > Mauro Carvalho Chehab (1):
> > >   drm/i915: gvt: fix kernel-doc trivial warnings
> > > 
> > > Paulo Miguel Almeida (1):
> > >   i915/gvt: remove hardcoded value on crc32_start calculation
> > > 
> > > Zhi Wang (1):
> > >   drm/i915/gvt: remove the vgpu->released and its sanity
> > > check
> > > 
> > > wangjianli (1):
> > >   drm/i915: fix repeated words in comments
> > > 
> > >  drivers/gpu/drm/i915/gvt/aperture_gm.c  | 4 ++--
> > >  drivers/gpu/drm/i915/gvt/cfg_space.c    | 2 +-
> > >  drivers/gpu/drm/i915/gvt/dmabuf.h   | 2 +-
> > >  drivers/gpu/drm/i915/gvt/firmware.c | 2 +-
> > >  drivers/gpu/drm/i915/gvt/gtt.c  | 9 ++---
> > >  drivers/gpu/drm/i915/gvt/gvt.h  | 2 --
> > >  drivers/gpu/drm/i915/gvt/handlers.c | 4 ++--
> > >  drivers/gpu/drm/i915/gvt/kvmgt.c    | 4 
> > >  drivers/gpu/drm/i915/gvt/mmio_context.c | 2 +-
> > >  drivers/gpu/drm/i915/gvt/page_track.c   | 2 +-
> > >  drivers/gpu/drm/i915/gvt/vgpu.c | 6 +++---
> > >  11 files changed, 14 insertions(+), 25 deletions(-)
> > 
> > 

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

[Zhenyu Wang]

On 2022.11.15 10:36:59 -0500, Rodrigo Vivi wrote:
> On Fri, Nov 11, 2022 at 04:59:03PM +0800, Zhenyu Wang wrote:
> > Hi,
> > 
> > Here's current accumulated changes in gvt-next. Sorry that I delayed
> > to refresh them on time for upstream...It contains mostly kernel doc,
> > typo fixes and small code cleanups, as details below.
> > 
> > btw, one gvt change for next https://patchwork.freedesktop.org/patch/58/
> > is still pending, I need a backmerge from linus tree e.g with recent 
> > vfio/mdev
> > consolidate change with gvt and Jason's fix for destroy device, to apply 
> > Zhi's
> > change cleanly. Pls help on that.
> > 
> > Thanks!
> > ---
> > The following changes since commit a6ebd538364b1e9e6048faaafbc0188172ed50c3:
> > 
> >   drm/i915/sdvo: Fix debug print (2022-10-28 14:46:21 +0300)
> > 
> > are available in the Git repository at:
> > 
> >   https://github.com/intel/gvt-linux.git tags/gvt-next-2022-11-11
> > 
> > for you to fetch changes up to 50468ca2e2e1ce882f060a8c263f678affe112db:
> > 
> >   drm/i915/gvt: Remove the unused function get_pt_type() (2022-11-08 
> > 15:34:06 +0800)
> > 
> > 
> > gvt-next-2022-11-11
> > 
> > - kernel doc fixes
> > - remove vgpu->released sanity check
> > - small clean up
> > 
> > 
> > Colin Ian King (1):
> >   drm/i915/reg: Fix spelling mistake "Unsupport" -> "Unsupported"
> 
> dim: d7e4e9579f01 ("drm/i915/reg: Fix spelling mistake "Unsupport" -> 
> "Unsupported""): committer Signed-off-by missing.
> 
> could you please fix this before we can merge this pr?
>

That should still be .mailmap issue for Colin's email...
But could we improve our dim script to grep mailmap in that case? So if s-o-b 
mail is valid
in mailmap, we should still allow it, right?

> > 
> > Jiapeng Chong (4):
> >   drm/i915/gvt: Fix kernel-doc
> >   drm/i915/gvt: Fix kernel-doc
> >   drm/i915/gvt: Fix kernel-doc
> >   drm/i915/gvt: Remove the unused function get_pt_type()
> > 
> > Julia Lawall (1):
> >   drm/i915/gvt: fix typo in comment
> > 
> > Mauro Carvalho Chehab (1):
> >   drm/i915: gvt: fix kernel-doc trivial warnings
> > 
> > Paulo Miguel Almeida (1):
> >   i915/gvt: remove hardcoded value on crc32_start calculation
> > 
> > Zhi Wang (1):
> >   drm/i915/gvt: remove the vgpu->released and its sanity check
> > 
> > wangjianli (1):
> >   drm/i915: fix repeated words in comments
> > 
> >  drivers/gpu/drm/i915/gvt/aperture_gm.c  | 4 ++--
> >  drivers/gpu/drm/i915/gvt/cfg_space.c| 2 +-
> >  drivers/gpu/drm/i915/gvt/dmabuf.h   | 2 +-
> >  drivers/gpu/drm/i915/gvt/firmware.c | 2 +-
> >  drivers/gpu/drm/i915/gvt/gtt.c  | 9 ++---
> >  drivers/gpu/drm/i915/gvt/gvt.h  | 2 --
> >  drivers/gpu/drm/i915/gvt/handlers.c | 4 ++--
> >  drivers/gpu/drm/i915/gvt/kvmgt.c| 4 
> >  drivers/gpu/drm/i915/gvt/mmio_context.c | 2 +-
> >  drivers/gpu/drm/i915/gvt/page_track.c   | 2 +-
> >  drivers/gpu/drm/i915/gvt/vgpu.c | 6 +++---
> >  11 files changed, 14 insertions(+), 25 deletions(-)
> 
> 


signature.asc
Description: PGP signature

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

[Rodrigo Vivi]

On Fri, Nov 11, 2022 at 04:59:03PM +0800, Zhenyu Wang wrote:
> Hi,
> 
> Here's current accumulated changes in gvt-next. Sorry that I delayed
> to refresh them on time for upstream...It contains mostly kernel doc,
> typo fixes and small code cleanups, as details below.
> 
> btw, one gvt change for next https://patchwork.freedesktop.org/patch/58/
> is still pending, I need a backmerge from linus tree e.g with recent vfio/mdev
> consolidate change with gvt and Jason's fix for destroy device, to apply Zhi's
> change cleanly. Pls help on that.
> 
> Thanks!
> ---
> The following changes since commit a6ebd538364b1e9e6048faaafbc0188172ed50c3:
> 
>   drm/i915/sdvo: Fix debug print (2022-10-28 14:46:21 +0300)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-2022-11-11
> 
> for you to fetch changes up to 50468ca2e2e1ce882f060a8c263f678affe112db:
> 
>   drm/i915/gvt: Remove the unused function get_pt_type() (2022-11-08 15:34:06 
> +0800)
> 
> 
> gvt-next-2022-11-11
> 
> - kernel doc fixes
> - remove vgpu->released sanity check
> - small clean up
> 
> 
> Colin Ian King (1):
>   drm/i915/reg: Fix spelling mistake "Unsupport" -> "Unsupported"

dim: d7e4e9579f01 ("drm/i915/reg: Fix spelling mistake "Unsupport" -> 
"Unsupported""): committer Signed-off-by missing.

could you please fix this before we can merge this pr?

> 
> Jiapeng Chong (4):
>   drm/i915/gvt: Fix kernel-doc
>   drm/i915/gvt: Fix kernel-doc
>   drm/i915/gvt: Fix kernel-doc
>   drm/i915/gvt: Remove the unused function get_pt_type()
> 
> Julia Lawall (1):
>   drm/i915/gvt: fix typo in comment
> 
> Mauro Carvalho Chehab (1):
>   drm/i915: gvt: fix kernel-doc trivial warnings
> 
> Paulo Miguel Almeida (1):
>   i915/gvt: remove hardcoded value on crc32_start calculation
> 
> Zhi Wang (1):
>   drm/i915/gvt: remove the vgpu->released and its sanity check
> 
> wangjianli (1):
>   drm/i915: fix repeated words in comments
> 
>  drivers/gpu/drm/i915/gvt/aperture_gm.c  | 4 ++--
>  drivers/gpu/drm/i915/gvt/cfg_space.c| 2 +-
>  drivers/gpu/drm/i915/gvt/dmabuf.h   | 2 +-
>  drivers/gpu/drm/i915/gvt/firmware.c | 2 +-
>  drivers/gpu/drm/i915/gvt/gtt.c  | 9 ++---
>  drivers/gpu/drm/i915/gvt/gvt.h  | 2 --
>  drivers/gpu/drm/i915/gvt/handlers.c | 4 ++--
>  drivers/gpu/drm/i915/gvt/kvmgt.c| 4 
>  drivers/gpu/drm/i915/gvt/mmio_context.c | 2 +-
>  drivers/gpu/drm/i915/gvt/page_track.c   | 2 +-
>  drivers/gpu/drm/i915/gvt/vgpu.c | 6 +++---
>  11 files changed, 14 insertions(+), 25 deletions(-)

Re: [Intel-gfx] [PULL] gvt-next-2022-04-29

[Jani Nikula]

On Thu, 28 Apr 2022, "Wang, Zhi A"  wrote:
> Hi folks:
>
> Here is the pull of gvt-next which fixes the compilation error and warnings
> for the the GVT-g refactor patches: 
>
> - Fix a compiling warning of non-static function only having one caller.
> - Fix a potential NULL pointer reference in the code re-factor.
> - Fix a compiling error when CONFIG_DRM_I915_DEBUG_RUNTIME_PM=n
>
> I also tried to apply this pull on the latest drm-inte-next and it succeeded
> without error and warnings.

Thanks again, pulled to drm-intel-next.

BR,
Jani.

>
> The following changes since commit 5e9ae5c47052e28a31fb4f55a6e735c28d4c3948:
>
>   drm/i915/gvt: Add missing symbol export. (2022-04-26 04:18:43 -0400)
>
> are available in the Git repository at:
>
>   https://github.com/intel/gvt-linux tags/gvt-next-2022-04-29
>
> for you to fetch changes up to 419f8299ddad6070a6c95aaedf78e50265871f36:
>
>   i915/gvt: Fix NULL pointer dereference in init_mmio_block_handlers 
> (2022-04-28 17:06:02 -0400)
>
> 
> gvt-next-2022-04-29
>
> Introduce fixes from previous pull.
> - Fix a compiling warning of non-static funtion only having one caller.
> - Fix a potential NULL pointer reference in the code re-factor.
> - Fix a compiling error when CONFIG_DRM_I915_DEBUG_RUNTIME_PM=n
>
> 
> Wan Jiabing (1):
>   i915/gvt: Fix NULL pointer dereference in init_mmio_block_handlers
>
> Zhi Wang (2):
>   drm/i915/gvt: Make intel_gvt_match_device() static
>   drm/i915/gvt: Fix the compiling error when 
> CONFIG_DRM_I915_DEBUG_RUNTIME_PM=n
>
>  drivers/gpu/drm/i915/gvt/handlers.c | 4 ++--
>  drivers/gpu/drm/i915/intel_gvt.c| 2 ++
>  2 files changed, 4 insertions(+), 2 deletions(-)

-- 
Jani Nikula, Intel Open Source Graphics Center

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

[Alex Williamson]

On Thu, 28 Apr 2022 15:35:58 -0600
Alex Williamson  wrote:

> On Tue, 26 Apr 2022 08:52:58 -0300
> Jason Gunthorpe  wrote:
> 
> > On Tue, Apr 26, 2022 at 08:42:25AM +, Wang, Zhi A wrote:  
> > > On 4/26/22 8:37 AM, Jani Nikula wrote:
> > > > On Tue, 26 Apr 2022, "Wang, Zhi A"  wrote:
> > > >> Hi folks:
> > > >>
> > > >> Here is the pull of gvt-next which fixs the compilation error when 
> > > >> i915 debug
> > > >> is open after the GVT-g refactor patches.
> > > >>
> > > >> Thanks so much for the efforts.
> > > > 
> > > > Pulled, thanks.
> > > > 
> > > > BR,
> > > > Jani.
> > > > 
> > > Thanks, looks good now. :)
> > 
> > Great! Thanks everyone!
> > 
> > Alex, can you pull this to VFIO now too? The top commit should be:  
> 
> I see a gvt-next-2022-04-29 tag adding the following fixes:
> 
> 419f8299ddad i915/gvt: Fix NULL pointer dereference in 
> init_mmio_block_handlers
> 5b95b9d58fb0 drm/i915/gvt: Fix the compiling error when 
> CONFIG_DRM_I915_DEBUG_RUNTIME_PM=n
> fa630c304b93 drm/i915/gvt: Make intel_gvt_match_device() static
> 
> I'm expecting that's my new merge target once a pull request is
> completed for that.  Please keep me cc'd.  Thanks,

Oops, I see the new pull request for this tag came in while I was
writing this.  I'll keep an eye for it to be merged.  Thanks,

Alex

> > commit 5e9ae5c47052e28a31fb4f55a6e735c28d4c3948
> > Author: Zhi Wang 
> > Date:   Mon Apr 25 18:03:31 2022 -0400
> > 
> > drm/i915/gvt: Add missing symbol export.
> > 
> > When CONFIG_DRM_I915_DEBUG_RUNTIME and CONFIG_DRM_I915_DEBUG_PM
> > are enabled, two more extra symols in i915 are required to be
> > exported.
> > 
> > Cc: Jani Nikula 
> > Signed-off-by: Zhi Wang 
> > Link: 
> > http://patchwork.freedesktop.org/patch/msgid/20220425220331.24865-1-zhi.a.w...@intel.com
> > Reviewed-by: Jani Nikula 
> > 
> > Which was picked up here:
> > 
> > https://cgit.freedesktop.org/drm-intel/commit/?h=drm-intel-next=f08699ec5bd924be4c9572e21fd0a806d3fb34c2
> > 
> > It will have these commits:
> > 
> > 5e9ae5c47052e2 drm/i915/gvt: Add missing symbol export.
> > 2917f53113be3b vfio/mdev: Remove mdev drvdata
> > 2aa72ec97ce9eb vfio/mdev: Use the driver core to create the 'remove' file
> > 6b42f491e17ce1 vfio/mdev: Remove mdev_parent_ops
> > e6486939d8ea22 vfio/mdev: Remove mdev_parent_ops dev_attr_groups
> > 6c7f98b334a32d vfio/mdev: Remove vfio_mdev.c
> > cba619cb0d4d66 drm/i915/gvt: merge gvt.c into kvmgvt.c
> > 978cf586ac35f3 drm/i915/gvt: convert to use vfio_register_emulated_iommu_dev
> > 0e09f4066ad11b drm/i915/gvt: remove kvmgt_guest_{init,exit}
> > 7f11e6893ff01b drm/i915/gvt: pass a struct intel_vgpu to the vfio 
> > read/write helpers
> > 4456641232e2c1 drm/i915/gvt: streamline intel_vgpu_create
> > 37e4bdbd5bad71 drm/i915/gvt: remove the extra vfio_device refcounting for 
> > dmabufs
> > 5f8f3fe67cd908 drm/i915/gvt: remove struct intel_gvt_mpt
> > 91879bbaf8890f drm/i915/gvt: devirtualize dma_pin_guest_page
> > 8398eee85fd009 drm/i915/gvt: devirtualize ->dma_{,un}map_guest_page
> > 4c2baaaf764bfb drm/i915/gvt: devirtualize ->{enable,disable}_page_track
> > 4050dab5981cd4 drm/i915/gvt: devirtualize ->gfn_to_mfn
> > bd73b4b193d450 drm/i915/gvt: devirtualize ->is_valid_gfn
> > b3bece34956f86 drm/i915/gvt: devirtualize ->inject_msi
> > 4c705ad0d784fd drm/i915/gvt: devirtualize ->detach_vgpu
> > f9399b0e4a9555 drm/i915/gvt: devirtualize ->set_edid and ->set_opregion
> > fe902f0ce686e8 drm/i915/gvt: devirtualize ->{get,put}_vfio_device
> > e3d7640eeeb306 drm/i915/gvt: devirtualize ->{read,write}_gpa
> > 3c340d05868d98 drm/i915/gvt: remove vgpu->handle
> > 10ddb96295f3bd drm/i915/gvt: merge struct kvmgt_guest_info into strut 
> > intel_vgpu
> > 62980cacc37f58 drm/i915/gvt: merge struct kvmgt_vdev into struct intel_vgpu
> > 3cbac24c2cdbfe drm/i915/gvt: remove the unused from_virt_to_mfn op
> > c977092a997708 drm/i915/gvt: remove the map_gfn_to_mfn and set_trap_area ops
> > 675e5c4a33e20c drm/i915/gvt: remove intel_gvt_ops
> > 8b750bf744181c drm/i915/gvt: move the gvt code into kvmgt.ko
> > f49fc35799fa63 drm/i915/gvt: rename intel_vgpu_ops to intel_vgpu_mdev_ops
> > 367748066eeb37 drm/i915/gvt: remove enum hypervisor_type
> > a85749e12d66c2 drm/i915/gvt: remove module refcounting in 
> > intel_gvt_{,un}register_hypervisor
> > 7f0cf30187cdb1 drm/i915/gvt: better align the Makefile with i915 Makefile
> > de5d437ae8696a drm/i915/gvt: fix trace TRACE_INCLUDE_PATH
> > 1672991412dfef i915/gvt: Use the initial HW state snapshot saved in i915
> > 66e7a8063381cb i915/gvt: Save the initial HW state snapshot in i915
> > e0f74ed4634d6d i915/gvt: Separate the MMIO tracking table from GVT-g
> > 
> > Thanks,
> > Jason
> >   
> 

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

[Alex Williamson]

On Tue, 26 Apr 2022 08:52:58 -0300
Jason Gunthorpe  wrote:

> On Tue, Apr 26, 2022 at 08:42:25AM +, Wang, Zhi A wrote:
> > On 4/26/22 8:37 AM, Jani Nikula wrote:  
> > > On Tue, 26 Apr 2022, "Wang, Zhi A"  wrote:  
> > >> Hi folks:
> > >>
> > >> Here is the pull of gvt-next which fixs the compilation error when i915 
> > >> debug
> > >> is open after the GVT-g refactor patches.
> > >>
> > >> Thanks so much for the efforts.  
> > > 
> > > Pulled, thanks.
> > > 
> > > BR,
> > > Jani.
> > >   
> > Thanks, looks good now. :)  
> 
> Great! Thanks everyone!
> 
> Alex, can you pull this to VFIO now too? The top commit should be:

I see a gvt-next-2022-04-29 tag adding the following fixes:

419f8299ddad i915/gvt: Fix NULL pointer dereference in init_mmio_block_handlers
5b95b9d58fb0 drm/i915/gvt: Fix the compiling error when 
CONFIG_DRM_I915_DEBUG_RUNTIME_PM=n
fa630c304b93 drm/i915/gvt: Make intel_gvt_match_device() static

I'm expecting that's my new merge target once a pull request is
completed for that.  Please keep me cc'd.  Thanks,

Alex

> commit 5e9ae5c47052e28a31fb4f55a6e735c28d4c3948
> Author: Zhi Wang 
> Date:   Mon Apr 25 18:03:31 2022 -0400
> 
> drm/i915/gvt: Add missing symbol export.
> 
> When CONFIG_DRM_I915_DEBUG_RUNTIME and CONFIG_DRM_I915_DEBUG_PM
> are enabled, two more extra symols in i915 are required to be
> exported.
> 
> Cc: Jani Nikula 
> Signed-off-by: Zhi Wang 
> Link: 
> http://patchwork.freedesktop.org/patch/msgid/20220425220331.24865-1-zhi.a.w...@intel.com
> Reviewed-by: Jani Nikula 
> 
> Which was picked up here:
> 
> https://cgit.freedesktop.org/drm-intel/commit/?h=drm-intel-next=f08699ec5bd924be4c9572e21fd0a806d3fb34c2
> 
> It will have these commits:
> 
> 5e9ae5c47052e2 drm/i915/gvt: Add missing symbol export.
> 2917f53113be3b vfio/mdev: Remove mdev drvdata
> 2aa72ec97ce9eb vfio/mdev: Use the driver core to create the 'remove' file
> 6b42f491e17ce1 vfio/mdev: Remove mdev_parent_ops
> e6486939d8ea22 vfio/mdev: Remove mdev_parent_ops dev_attr_groups
> 6c7f98b334a32d vfio/mdev: Remove vfio_mdev.c
> cba619cb0d4d66 drm/i915/gvt: merge gvt.c into kvmgvt.c
> 978cf586ac35f3 drm/i915/gvt: convert to use vfio_register_emulated_iommu_dev
> 0e09f4066ad11b drm/i915/gvt: remove kvmgt_guest_{init,exit}
> 7f11e6893ff01b drm/i915/gvt: pass a struct intel_vgpu to the vfio read/write 
> helpers
> 4456641232e2c1 drm/i915/gvt: streamline intel_vgpu_create
> 37e4bdbd5bad71 drm/i915/gvt: remove the extra vfio_device refcounting for 
> dmabufs
> 5f8f3fe67cd908 drm/i915/gvt: remove struct intel_gvt_mpt
> 91879bbaf8890f drm/i915/gvt: devirtualize dma_pin_guest_page
> 8398eee85fd009 drm/i915/gvt: devirtualize ->dma_{,un}map_guest_page
> 4c2baaaf764bfb drm/i915/gvt: devirtualize ->{enable,disable}_page_track
> 4050dab5981cd4 drm/i915/gvt: devirtualize ->gfn_to_mfn
> bd73b4b193d450 drm/i915/gvt: devirtualize ->is_valid_gfn
> b3bece34956f86 drm/i915/gvt: devirtualize ->inject_msi
> 4c705ad0d784fd drm/i915/gvt: devirtualize ->detach_vgpu
> f9399b0e4a9555 drm/i915/gvt: devirtualize ->set_edid and ->set_opregion
> fe902f0ce686e8 drm/i915/gvt: devirtualize ->{get,put}_vfio_device
> e3d7640eeeb306 drm/i915/gvt: devirtualize ->{read,write}_gpa
> 3c340d05868d98 drm/i915/gvt: remove vgpu->handle
> 10ddb96295f3bd drm/i915/gvt: merge struct kvmgt_guest_info into strut 
> intel_vgpu
> 62980cacc37f58 drm/i915/gvt: merge struct kvmgt_vdev into struct intel_vgpu
> 3cbac24c2cdbfe drm/i915/gvt: remove the unused from_virt_to_mfn op
> c977092a997708 drm/i915/gvt: remove the map_gfn_to_mfn and set_trap_area ops
> 675e5c4a33e20c drm/i915/gvt: remove intel_gvt_ops
> 8b750bf744181c drm/i915/gvt: move the gvt code into kvmgt.ko
> f49fc35799fa63 drm/i915/gvt: rename intel_vgpu_ops to intel_vgpu_mdev_ops
> 367748066eeb37 drm/i915/gvt: remove enum hypervisor_type
> a85749e12d66c2 drm/i915/gvt: remove module refcounting in 
> intel_gvt_{,un}register_hypervisor
> 7f0cf30187cdb1 drm/i915/gvt: better align the Makefile with i915 Makefile
> de5d437ae8696a drm/i915/gvt: fix trace TRACE_INCLUDE_PATH
> 1672991412dfef i915/gvt: Use the initial HW state snapshot saved in i915
> 66e7a8063381cb i915/gvt: Save the initial HW state snapshot in i915
> e0f74ed4634d6d i915/gvt: Separate the MMIO tracking table from GVT-g
> 
> Thanks,
> Jason
> 

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

[Robert Beckett]

On 26/04/2022 17:58, Wang, Zhi A wrote:

On 4/26/22 3:53 PM, Jason Gunthorpe wrote:

On Tue, Apr 26, 2022 at 07:58:59AM +, Wang, Zhi A wrote:

Hi folks:

Here is the pull of gvt-next which fixs the compilation error when i915 debug
is open after the GVT-g refactor patches.

Thanks so much for the efforts.

Thanks,
Zhi.

The following changes since commit 2917f53113be3b7a0f374e02cebe6d6b749366b5:

   vfio/mdev: Remove mdev drvdata (2022-04-21 07:36:56 -0400)

are available in the Git repository at:

   https://github.com/intel/gvt-linux tags/gvt-next-2022-04-26

for you to fetch changes up to 2da299cee780ea797b3f72558687868072cf5eb5:

   drm/i915/gvt: Add missing export of symbols. (2022-04-25 18:03:04 -0400)

gvt-next-2022-04-26

- Add two missing exports of symbols when i915 debug is enabled.

Zhi Wang (1):
   drm/i915/gvt: Add missing export of symbols.

  drivers/gpu/drm/i915/intel_gvt.c | 2 ++
  1 file changed, 2 insertions(+)


This still has another compile problem:

ERROR: modpost: "intel_runtime_pm_put" [vmlinux] is a static EXPORT_SYMBOL_GPL

Because:

#if IS_ENABLED(CONFIG_DRM_I915_DEBUG_RUNTIME_PM)
void intel_runtime_pm_put(struct intel_runtime_pm *rpm, intel_wakeref_t wref);
#else
static inline void
intel_runtime_pm_put(struct intel_runtime_pm *rpm, intel_wakeref_t wref)
{
 intel_runtime_pm_put_unchecked(rpm);
}
#endif

Looks like it happens if CONFIG_DRM_I915_DEBUG_RUNTIME_PM=n

I think you probably want to #ifdef the export in the same way:

--- a/drivers/gpu/drm/i915/intel_gvt.c
+++ b/drivers/gpu/drm/i915/intel_gvt.c
@@ -309,7 +309,9 @@ EXPORT_SYMBOL_NS_GPL(__intel_context_do_pin, I915_GVT);
  EXPORT_SYMBOL_NS_GPL(__intel_context_do_unpin, I915_GVT);
  EXPORT_SYMBOL_NS_GPL(intel_ring_begin, I915_GVT);
  EXPORT_SYMBOL_NS_GPL(intel_runtime_pm_get, I915_GVT);
+#if IS_ENABLED(CONFIG_DRM_I915_DEBUG_RUNTIME_PM)
  EXPORT_SYMBOL_NS_GPL(intel_runtime_pm_put, I915_GVT);
+#endif

Sigh. That's tricky. Let me prepare another one.


Also the following compile error:

drivers/gpu/drm/i915/gvt/handlers.c:75:6: error: no previous prototype 
for ‘intel_gvt_match_device’ [-Werror=missing-prototypes]


   75 | bool intel_gvt_match_device(struct intel_gvt *gvt,

  |  ^~


it was removed from a header. The implementation should now be made static


  EXPORT_SYMBOL_NS_GPL(intel_runtime_pm_put_unchecked, I915_GVT);
  EXPORT_SYMBOL_NS_GPL(intel_uncore_forcewake_for_reg, I915_GVT);
  EXPORT_SYMBOL_NS_GPL(intel_uncore_forcewake_get, I915_GVT);

Jason

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

[Wang, Zhi A]

On 4/26/22 3:53 PM, Jason Gunthorpe wrote:
> On Tue, Apr 26, 2022 at 07:58:59AM +, Wang, Zhi A wrote:
>> Hi folks:
>>
>> Here is the pull of gvt-next which fixs the compilation error when i915 debug
>> is open after the GVT-g refactor patches.
>>
>> Thanks so much for the efforts.
>>
>> Thanks,
>> Zhi.
>>
>> The following changes since commit 2917f53113be3b7a0f374e02cebe6d6b749366b5:
>>
>>   vfio/mdev: Remove mdev drvdata (2022-04-21 07:36:56 -0400)
>>
>> are available in the Git repository at:
>>
>>   https://github.com/intel/gvt-linux tags/gvt-next-2022-04-26
>>
>> for you to fetch changes up to 2da299cee780ea797b3f72558687868072cf5eb5:
>>
>>   drm/i915/gvt: Add missing export of symbols. (2022-04-25 18:03:04 -0400)
>>
>> gvt-next-2022-04-26
>>
>> - Add two missing exports of symbols when i915 debug is enabled.
>>
>> Zhi Wang (1):
>>   drm/i915/gvt: Add missing export of symbols.
>>
>>  drivers/gpu/drm/i915/intel_gvt.c | 2 ++
>>  1 file changed, 2 insertions(+)
> 
> This still has another compile problem:
> 
> ERROR: modpost: "intel_runtime_pm_put" [vmlinux] is a static EXPORT_SYMBOL_GPL
> 
> Because:
> 
> #if IS_ENABLED(CONFIG_DRM_I915_DEBUG_RUNTIME_PM)
> void intel_runtime_pm_put(struct intel_runtime_pm *rpm, intel_wakeref_t wref);
> #else
> static inline void
> intel_runtime_pm_put(struct intel_runtime_pm *rpm, intel_wakeref_t wref)
> {
> intel_runtime_pm_put_unchecked(rpm);
> }
> #endif
> 
> Looks like it happens if CONFIG_DRM_I915_DEBUG_RUNTIME_PM=n
> 
> I think you probably want to #ifdef the export in the same way:
> 
> --- a/drivers/gpu/drm/i915/intel_gvt.c
> +++ b/drivers/gpu/drm/i915/intel_gvt.c
> @@ -309,7 +309,9 @@ EXPORT_SYMBOL_NS_GPL(__intel_context_do_pin, I915_GVT);
>  EXPORT_SYMBOL_NS_GPL(__intel_context_do_unpin, I915_GVT);
>  EXPORT_SYMBOL_NS_GPL(intel_ring_begin, I915_GVT);
>  EXPORT_SYMBOL_NS_GPL(intel_runtime_pm_get, I915_GVT);
> +#if IS_ENABLED(CONFIG_DRM_I915_DEBUG_RUNTIME_PM)
>  EXPORT_SYMBOL_NS_GPL(intel_runtime_pm_put, I915_GVT);
> +#endif
Sigh. That's tricky. Let me prepare another one. 
>  EXPORT_SYMBOL_NS_GPL(intel_runtime_pm_put_unchecked, I915_GVT);
>  EXPORT_SYMBOL_NS_GPL(intel_uncore_forcewake_for_reg, I915_GVT);
>  EXPORT_SYMBOL_NS_GPL(intel_uncore_forcewake_get, I915_GVT);
> 
> Jason
> 

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

[Wang, Zhi A]

On 4/26/22 8:37 AM, Jani Nikula wrote:
> On Tue, 26 Apr 2022, "Wang, Zhi A"  wrote:
>> Hi folks:
>>
>> Here is the pull of gvt-next which fixs the compilation error when i915 debug
>> is open after the GVT-g refactor patches.
>>
>> Thanks so much for the efforts.
> 
> Pulled, thanks.
> 
> BR,
> Jani.
> 
Thanks, looks good now. :)

thanks,
Zhi.
>>
>> Thanks,
>> Zhi.
>>
>> The following changes since commit 2917f53113be3b7a0f374e02cebe6d6b749366b5:
>>
>>   vfio/mdev: Remove mdev drvdata (2022-04-21 07:36:56 -0400)
>>
>> are available in the Git repository at:
>>
>>   https://github.com/intel/gvt-linux tags/gvt-next-2022-04-26
>>
>> for you to fetch changes up to 2da299cee780ea797b3f72558687868072cf5eb5:
>>
>>   drm/i915/gvt: Add missing export of symbols. (2022-04-25 18:03:04 -0400)
>>
>> 
>> gvt-next-2022-04-26
>>
>> - Add two missing exports of symbols when i915 debug is enabled.
>>
>> 
>> Zhi Wang (1):
>>   drm/i915/gvt: Add missing export of symbols.
>>
>>  drivers/gpu/drm/i915/intel_gvt.c | 2 ++
>>  1 file changed, 2 insertions(+)
> 

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

[Wang, Zhi A]

On 4/26/22 8:37 AM, Jani Nikula wrote:
> On Tue, 26 Apr 2022, "Wang, Zhi A"  wrote:
>> Hi folks:
>>
>> Here is the pull of gvt-next which fixs the compilation error when i915 debug
>> is open after the GVT-g refactor patches.
>>
>> Thanks so much for the efforts.
> 
> Pulled, thanks.
> 
> BR,
> Jani.
> 
>>
I just updated the branch. Can you check a little bit if you got the newest one?
>> Thanks,
>> Zhi.
>>
>> The following changes since commit 2917f53113be3b7a0f374e02cebe6d6b749366b5:
>>
>>   vfio/mdev: Remove mdev drvdata (2022-04-21 07:36:56 -0400)
>>
>> are available in the Git repository at:
>>
>>   https://github.com/intel/gvt-linux tags/gvt-next-2022-04-26
>>
>> for you to fetch changes up to 2da299cee780ea797b3f72558687868072cf5eb5:
>>
>>   drm/i915/gvt: Add missing export of symbols. (2022-04-25 18:03:04 -0400)
>>
>> 
>> gvt-next-2022-04-26
>>
>> - Add two missing exports of symbols when i915 debug is enabled.
>>
>> 
>> Zhi Wang (1):
>>   drm/i915/gvt: Add missing export of symbols.
>>
>>  drivers/gpu/drm/i915/intel_gvt.c | 2 ++
>>  1 file changed, 2 insertions(+)
> 

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

[Jani Nikula]

On Tue, 26 Apr 2022, "Wang, Zhi A"  wrote:
> Hi folks:
>
> Here is the pull of gvt-next which fixs the compilation error when i915 debug
> is open after the GVT-g refactor patches.
>
> Thanks so much for the efforts.

Pulled, thanks.

BR,
Jani.

>
> Thanks,
> Zhi.
>
> The following changes since commit 2917f53113be3b7a0f374e02cebe6d6b749366b5:
>
>   vfio/mdev: Remove mdev drvdata (2022-04-21 07:36:56 -0400)
>
> are available in the Git repository at:
>
>   https://github.com/intel/gvt-linux tags/gvt-next-2022-04-26
>
> for you to fetch changes up to 2da299cee780ea797b3f72558687868072cf5eb5:
>
>   drm/i915/gvt: Add missing export of symbols. (2022-04-25 18:03:04 -0400)
>
> 
> gvt-next-2022-04-26
>
> - Add two missing exports of symbols when i915 debug is enabled.
>
> 
> Zhi Wang (1):
>   drm/i915/gvt: Add missing export of symbols.
>
>  drivers/gpu/drm/i915/intel_gvt.c | 2 ++
>  1 file changed, 2 insertions(+)

-- 
Jani Nikula, Intel Open Source Graphics Center

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

[Wang, Zhi A]

On 4/20/22 3:02 PM, Jason Gunthorpe wrote:
> On Wed, Apr 20, 2022 at 02:41:04PM +, Wang, Zhi A wrote:
>> On 4/20/22 12:13 PM, Jason Gunthorpe wrote:
>>> On Wed, Apr 20, 2022 at 08:04:31AM +, Wang, Zhi A wrote:
 Hi folks:

 Here is the PR of gvt-next.

 Mostly it includes the patch bundle of GVT-g re-factor patches for 
 adapting the GVT-g with the
 new MDEV interfaces:

 - Separating the MMIO table from GVT-g. (Zhi)
 - GVT-g re-factor. (Christoph)
 - GVT-g mdev API cleanup. (Jason)
 - GVT-g trace/makefile cleanup. (Jani)

 Thanks so much for making this happen.

 This PR has been tested as following and no problem shows up:

 $dim update-branches
 $dim apply-pull drm-intel-next < this_email.eml

 The following changes since commit 
 b39d2c6202426b560641e5800c5523851b5db586:

   drm/i915/fbc: Call intel_fbc_activate() directly from frontbuffer flush 
 (2022-04-13 17:20:49 +0300)
>>>
>>> ??
>>>
>>> Why did you rebase this again? It needs to be on a rc release tag as
>>> you had in your github, not whatever this is.
>>>
>> Hi Jason:
>>
>> Here is what I understand, the pull going to the drm-intel-next
>> needs to be based on drm-intel-next from the branch gvt-next. 
> 
> No, there cannot be two pulls, as I explained when using topic
> branches you must never rebase.
> 
>> The pull going to the VFIO needs to be based on -rc, the
>> topic/for-christoph brnach.
> 
> Yes, so what you need to do is:
> 
> # Get a clean tree on drm-intel-next
> $ git worktree add /tmp/gvt-next
> Preparing worktree (new branch 'gvt-next')
> $ cd /tmp/gvt-next
> $ git reset --hard b39d2c6202426b560641e5800c5523851b5db586  # drm-intel-next 
> commit you tested
> 
> # Merge Christoph's topic:
> $ git fetch https://github.com/intel/gvt-linux.git topic/for-christoph
> $ git merge FETCH_HEAD
> Auto-merging drivers/gpu/drm/i915/Makefile
> Auto-merging drivers/gpu/drm/i915/gvt/handlers.c
> Auto-merging drivers/gpu/drm/i915/i915_driver.c
> Auto-merging drivers/gpu/drm/i915/i915_drv.h
> Merge made by the 'ort' strategy.
> 
Exactly what I did on my branch except that I sent the pull request based on my 
gvt-next. :(
> [..
> Merge branch 'topic/for-christoph' of https://github.com/intel/gvt-linux into 
> gvt-next
> 
> # By Christoph Hellwig (27) and others
> # Via Zhi Wang
> * 'topic/for-christoph' of https://github.com/intel/gvt-linux: (37 commits)
> ]
> 
> And then check it against what you prepared in this PR here:
> 
> $ git diff HEAD 888471711a80b22c53547f3a625f20f487714f28
> [empty]
> 
> *do not rebase a topic branch* this is very important.
> 
> Now - given that we can see there is no merge conflict you don't need
> to do anything! Just send topic/for-christoph, exactly as-it-is to
> drm-intel-next as a PR and that is all.
> 
>> Sorry this is way too complicated to me. Let me prepare the new pull
>> as what you ask. Shall I send the exact same pull to i915 and VFIO ?
> 
> Yes, exact same, this is important.
> 
> You were very close before, the only issue was rebasing
> topic/for-christoph instead of merging.
>
I will send it by the end of the day. Thanks so much for your patience.
 
> Jason
> 

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

[Wang, Zhi A]

On 4/20/22 12:13 PM, Jason Gunthorpe wrote:
> On Wed, Apr 20, 2022 at 08:04:31AM +, Wang, Zhi A wrote:
>> Hi folks:
>>
>> Here is the PR of gvt-next.
>>
>> Mostly it includes the patch bundle of GVT-g re-factor patches for adapting 
>> the GVT-g with the
>> new MDEV interfaces:
>>
>> - Separating the MMIO table from GVT-g. (Zhi)
>> - GVT-g re-factor. (Christoph)
>> - GVT-g mdev API cleanup. (Jason)
>> - GVT-g trace/makefile cleanup. (Jani)
>>
>> Thanks so much for making this happen.
>>
>> This PR has been tested as following and no problem shows up:
>>
>> $dim update-branches
>> $dim apply-pull drm-intel-next < this_email.eml
>>
>> The following changes since commit b39d2c6202426b560641e5800c5523851b5db586:
>>
>>   drm/i915/fbc: Call intel_fbc_activate() directly from frontbuffer flush 
>> (2022-04-13 17:20:49 +0300)
> 
> ??
> 
> Why did you rebase this again? It needs to be on a rc release tag as
> you had in your github, not whatever this is.
> 
Hi Jason:

Here is what I understand, the pull going to the drm-intel-next needs to be 
based on drm-intel-next from the branch gvt-next. The pull going to the VFIO 
needs to be based on -rc, the topic/for-christoph brnach. So I did a merge from 
topic/for-christoph to my gvt-next branch and sent this pull, so that our QA 
can test these bundle on the gvt-staging branch.

Sorry this is way too complicated to me. Let me prepare the new pull as what 
you ask. Shall I send the exact same pull to i915 and VFIO ?

Thanks,
Zhi.

> Jason
> 

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

[Jani Nikula]

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 
> 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

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

[Jani Nikula]

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.
> --
> 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

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

[Jani Nikula]

On Tue, 16 Mar 2021, Zhenyu Wang  wrote:
> Hi,
>
> This is queued gvt-next pull for 5.13. Mostly it's for accurate
> vGPU virtual display rate tracking and change for per-vGPU vblank
> timer based on that, which brings accurate vblank injection.

Pulled to drm-intel-next.

BR,
Jani.

>
> Thanks
> --
> The following changes since commit c73927183f2b85bf1a06d75d2b51be72aff42358:
>
>   drm/i915/tgl+: Sanitize the DDI LANES/IO and AUX power domain names 
> (2021-02-24 14:05:39 +0200)
>
> are available in the Git repository at:
>
>   https://github.com/intel/gvt-linux.git tags/gvt-next-2021-03-16
>
> for you to fetch changes up to 9317f356df83a5caeccae2e343d1a569929bcfc9:
>
>   drm/i915/gvt: Fixed couple of spellings in the file gtt.c (2021-03-01 
> 14:02:14 +0800)
>
> 
> gvt-next-2021-03-16
>
> - Parse accurate vGPU virtual display rate (Colin)
> - Convert vblank timer as per-vGPU based on current rate (Colin)
> - spelling fix (Bhaskar)
>
> 
> Bhaskar Chowdhury (1):
>   drm/i915/gvt: Fixed couple of spellings in the file gtt.c
>
> Colin Xu (2):
>   drm/i915/gvt: Get accurate vGPU virtual display refresh rate from vreg
>   drm/i915/gvt: Refactor GVT vblank emulator for vGPU virtual display
>
>  drivers/gpu/drm/i915/gvt/display.c   | 107 +++---
>  drivers/gpu/drm/i915/gvt/display.h   |  14 +-
>  drivers/gpu/drm/i915/gvt/gtt.c   |   4 +-
>  drivers/gpu/drm/i915/gvt/gvt.c   |  25 +++-
>  drivers/gpu/drm/i915/gvt/gvt.h   |  13 +-
>  drivers/gpu/drm/i915/gvt/handlers.c  | 261 
> ++-
>  drivers/gpu/drm/i915/gvt/interrupt.c |  37 -
>  drivers/gpu/drm/i915/gvt/interrupt.h |   7 -
>  drivers/gpu/drm/i915/gvt/vgpu.c  |   2 -
>  9 files changed, 355 insertions(+), 115 deletions(-)
>
> ___
> 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 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

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  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

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

[Jani Nikula]

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, 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

[Zhenyu Wang]

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


signature.asc
Description: PGP signature
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Joonas Lahtinen]

Quoting Zhenyu Wang (2020-11-24 05:13:59)
> On 2020.11.23 11:32:38 +0200, Joonas Lahtinen wrote:
> > Quoting Zhenyu Wang (2020-11-23 11:05:17)
> > > 
> > > Hi,
> > > 
> > > Here's gvt next pull for v5.11. Mostly it's for host suspend/resume
> > > fix with vGPU active and with some other enhancement as details below.
> > > Note that this includes some minor i915 driver change to add gvt hook
> > > in suspend/resume function which has been sent and reviewed on
> > > intel-gfx list.
> > > 
> > > I just generated against drm-intel-next-queued-2020-11-03 which this
> > > tree bases on now. Let me know if there's any issue in merge.
> > 
> > Sometimes GVT changes are paired with changes related the i915 side
> > to adjust the running virtual clients. The changes are more often
> > related to GT side, but there's also been display related changes.
> > 
> > Going forward, would we want to continue to apply gvt-next to
> > drm-intel-next (-queued is planned to be deprecated) or
> > should we use drm-intel-gt-next?
> >
> 
> Is there any clear criteria on patches for -next or -gt-next now?
> Something might be only gvt specific, e.g we'll have some enhancement patches
> for guest context parse, this might be considered as 'gt' part? I'm not sure.
> But yes, I hope we just stick with one, currently thinking drm-intel-next.

For anything self-contained in gvt directory only, we can make a choice.

I think the patches that concern vgpu, have most often been around the GT
related code (opposed to display and PM).

That kind of makes me think we would get away with least amount of topic
branches and backmerges in the future if we also merged gvt-next to
drm-intel-gt-next. Thoughts?

That'd just mean a shift in timeline to send gvt-next latest early in -rc4
week.

Regards, Joonas

> > Or should we always strictly apply the GVT changes to drm-intel-next,
> > and then any related i915 changes to drm-intel-next or drm-intel-gt-next
> > depending on which one they are related to?
> >
> 
> How about basically we just apply to drm-intel-next, but there might be gvt
> specific pull required for -gt-next e.g ww-lock fixes? I think we can do that 
> way
> now to see if there'll be any real issue popup.
> 
> Thanks
> 
> > 
> > > Thanks
> > > --
> > > The following changes since commit 
> > > 139caf7ca2866cd0a45814ff938cb0c33920a266:
> > > 
> > >   drm/i915: Update DRIVER_DATE to 20201103 (2020-11-03 14:21:25 +0200)
> > > 
> > > are available in the Git repository at:
> > > 
> > >   https://github.com/intel/gvt-linux tags/gvt-next-2020-11-23
> > > 
> > > for you to fetch changes up to 9a3a238b3de97b4210c6de66aa88b2d7021ac086:
> > > 
> > >   drm/i915/gvt: treat intel_gvt_mpt as const in gvt code (2020-11-23 
> > > 17:14:20 +0800)
> > > 
> > > 
> > > gvt-next-2020-11-23
> > > 
> > > - Fix host suspend/resume with vGPU (Colin)
> > > - optimize idr init (Varma)
> > > - Change intel_gvt_mpt as const (Julian)
> > > - One comment error fix (Yan)
> > > 
> > > 
> > > Colin Xu (3):
> > >   drm/i915/gvt: Save/restore HW status to support GVT suspend/resume
> > >   drm/i915: Add GVT resume routine to i915
> > >   drm/i915/gvt: Fix virtual display setup for BXT/APL
> > > 
> > > Deepak R Varma (1):
> > >   drm/i915/gvt: replace idr_init() by idr_init_base()
> > > 
> > > Julian Stecklina (1):
> > >   drm/i915/gvt: treat intel_gvt_mpt as const in gvt code
> > > 
> > > Yan Zhao (1):
> > >   drm/i915/gvt: correct a false comment of flag F_UNALIGN
> > > 
> > >  drivers/gpu/drm/i915/gvt/display.c  | 179 
> > > 
> > >  drivers/gpu/drm/i915/gvt/gtt.c  |  64 +
> > >  drivers/gpu/drm/i915/gvt/gtt.h  |   4 +
> > >  drivers/gpu/drm/i915/gvt/gvt.c  |  13 ++-
> > >  drivers/gpu/drm/i915/gvt/gvt.h  |   7 +-
> > >  drivers/gpu/drm/i915/gvt/handlers.c |  44 -
> > >  drivers/gpu/drm/i915/gvt/kvmgt.c|   2 +-
> > >  drivers/gpu/drm/i915/gvt/mmio.c |   5 +
> > >  drivers/gpu/drm/i915/gvt/mmio.h |   4 +
> > >  drivers/gpu/drm/i915/gvt/mpt.h  |   2 +-
> > >  drivers/gpu/drm/i915/gvt/vgpu.c |   2 +-
> > >  drivers/gpu/drm/i915/i915_drv.c |   2 +
> > >  drivers/gpu/drm/i915/intel_gvt.c|  15 +++
> > >  drivers/gpu/drm/i915/intel_gvt.h|   5 +
> > >  14 files changed, 338 insertions(+), 10 deletions(-)
> > > 
> > > -- 
> > > 
> > > $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
> > ___
> > intel-gvt-dev mailing list
> > intel-gvt-...@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev
> 
> -- 
> 
> $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

[Jani Nikula]

On Tue, 24 Nov 2020, Zhenyu Wang  wrote:
> On 2020.11.23 11:32:38 +0200, Joonas Lahtinen wrote:
>> Quoting Zhenyu Wang (2020-11-23 11:05:17)
>> > 
>> > Hi,
>> > 
>> > Here's gvt next pull for v5.11. Mostly it's for host suspend/resume
>> > fix with vGPU active and with some other enhancement as details below.
>> > Note that this includes some minor i915 driver change to add gvt hook
>> > in suspend/resume function which has been sent and reviewed on
>> > intel-gfx list.
>> > 
>> > I just generated against drm-intel-next-queued-2020-11-03 which this
>> > tree bases on now. Let me know if there's any issue in merge.
>> 
>> Sometimes GVT changes are paired with changes related the i915 side
>> to adjust the running virtual clients. The changes are more often
>> related to GT side, but there's also been display related changes.
>> 
>> Going forward, would we want to continue to apply gvt-next to
>> drm-intel-next (-queued is planned to be deprecated) or
>> should we use drm-intel-gt-next?
>>
>
> Is there any clear criteria on patches for -next or -gt-next now?
> Something might be only gvt specific, e.g we'll have some enhancement patches
> for guest context parse, this might be considered as 'gt' part? I'm not sure.
> But yes, I hope we just stick with one, currently thinking drm-intel-next.
>
>> Or should we always strictly apply the GVT changes to drm-intel-next,
>> and then any related i915 changes to drm-intel-next or drm-intel-gt-next
>> depending on which one they are related to?
>>
>
> How about basically we just apply to drm-intel-next, but there might be gvt
> specific pull required for -gt-next e.g ww-lock fixes? I think we can do that 
> way
> now to see if there'll be any real issue popup.

Pulled to drm-intel-next-queued now.

Thanks,
Jani.


>
> Thanks
>
>> 
>> > Thanks
>> > --
>> > The following changes since commit 
>> > 139caf7ca2866cd0a45814ff938cb0c33920a266:
>> > 
>> >   drm/i915: Update DRIVER_DATE to 20201103 (2020-11-03 14:21:25 +0200)
>> > 
>> > are available in the Git repository at:
>> > 
>> >   https://github.com/intel/gvt-linux tags/gvt-next-2020-11-23
>> > 
>> > for you to fetch changes up to 9a3a238b3de97b4210c6de66aa88b2d7021ac086:
>> > 
>> >   drm/i915/gvt: treat intel_gvt_mpt as const in gvt code (2020-11-23 
>> > 17:14:20 +0800)
>> > 
>> > 
>> > gvt-next-2020-11-23
>> > 
>> > - Fix host suspend/resume with vGPU (Colin)
>> > - optimize idr init (Varma)
>> > - Change intel_gvt_mpt as const (Julian)
>> > - One comment error fix (Yan)
>> > 
>> > 
>> > Colin Xu (3):
>> >   drm/i915/gvt: Save/restore HW status to support GVT suspend/resume
>> >   drm/i915: Add GVT resume routine to i915
>> >   drm/i915/gvt: Fix virtual display setup for BXT/APL
>> > 
>> > Deepak R Varma (1):
>> >   drm/i915/gvt: replace idr_init() by idr_init_base()
>> > 
>> > Julian Stecklina (1):
>> >   drm/i915/gvt: treat intel_gvt_mpt as const in gvt code
>> > 
>> > Yan Zhao (1):
>> >   drm/i915/gvt: correct a false comment of flag F_UNALIGN
>> > 
>> >  drivers/gpu/drm/i915/gvt/display.c  | 179 
>> > 
>> >  drivers/gpu/drm/i915/gvt/gtt.c  |  64 +
>> >  drivers/gpu/drm/i915/gvt/gtt.h  |   4 +
>> >  drivers/gpu/drm/i915/gvt/gvt.c  |  13 ++-
>> >  drivers/gpu/drm/i915/gvt/gvt.h  |   7 +-
>> >  drivers/gpu/drm/i915/gvt/handlers.c |  44 -
>> >  drivers/gpu/drm/i915/gvt/kvmgt.c|   2 +-
>> >  drivers/gpu/drm/i915/gvt/mmio.c |   5 +
>> >  drivers/gpu/drm/i915/gvt/mmio.h |   4 +
>> >  drivers/gpu/drm/i915/gvt/mpt.h  |   2 +-
>> >  drivers/gpu/drm/i915/gvt/vgpu.c |   2 +-
>> >  drivers/gpu/drm/i915/i915_drv.c |   2 +
>> >  drivers/gpu/drm/i915/intel_gvt.c|  15 +++
>> >  drivers/gpu/drm/i915/intel_gvt.h|   5 +
>> >  14 files changed, 338 insertions(+), 10 deletions(-)
>> > 
>> > -- 
>> > 
>> > $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
>> ___
>> intel-gvt-dev mailing list
>> intel-gvt-...@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev

-- 
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

[Zhenyu Wang]

On 2020.11.23 11:32:38 +0200, Joonas Lahtinen wrote:
> Quoting Zhenyu Wang (2020-11-23 11:05:17)
> > 
> > Hi,
> > 
> > Here's gvt next pull for v5.11. Mostly it's for host suspend/resume
> > fix with vGPU active and with some other enhancement as details below.
> > Note that this includes some minor i915 driver change to add gvt hook
> > in suspend/resume function which has been sent and reviewed on
> > intel-gfx list.
> > 
> > I just generated against drm-intel-next-queued-2020-11-03 which this
> > tree bases on now. Let me know if there's any issue in merge.
> 
> Sometimes GVT changes are paired with changes related the i915 side
> to adjust the running virtual clients. The changes are more often
> related to GT side, but there's also been display related changes.
> 
> Going forward, would we want to continue to apply gvt-next to
> drm-intel-next (-queued is planned to be deprecated) or
> should we use drm-intel-gt-next?
>

Is there any clear criteria on patches for -next or -gt-next now?
Something might be only gvt specific, e.g we'll have some enhancement patches
for guest context parse, this might be considered as 'gt' part? I'm not sure.
But yes, I hope we just stick with one, currently thinking drm-intel-next.

> Or should we always strictly apply the GVT changes to drm-intel-next,
> and then any related i915 changes to drm-intel-next or drm-intel-gt-next
> depending on which one they are related to?
>

How about basically we just apply to drm-intel-next, but there might be gvt
specific pull required for -gt-next e.g ww-lock fixes? I think we can do that 
way
now to see if there'll be any real issue popup.

Thanks

> 
> > Thanks
> > --
> > The following changes since commit 139caf7ca2866cd0a45814ff938cb0c33920a266:
> > 
> >   drm/i915: Update DRIVER_DATE to 20201103 (2020-11-03 14:21:25 +0200)
> > 
> > are available in the Git repository at:
> > 
> >   https://github.com/intel/gvt-linux tags/gvt-next-2020-11-23
> > 
> > for you to fetch changes up to 9a3a238b3de97b4210c6de66aa88b2d7021ac086:
> > 
> >   drm/i915/gvt: treat intel_gvt_mpt as const in gvt code (2020-11-23 
> > 17:14:20 +0800)
> > 
> > 
> > gvt-next-2020-11-23
> > 
> > - Fix host suspend/resume with vGPU (Colin)
> > - optimize idr init (Varma)
> > - Change intel_gvt_mpt as const (Julian)
> > - One comment error fix (Yan)
> > 
> > 
> > Colin Xu (3):
> >   drm/i915/gvt: Save/restore HW status to support GVT suspend/resume
> >   drm/i915: Add GVT resume routine to i915
> >   drm/i915/gvt: Fix virtual display setup for BXT/APL
> > 
> > Deepak R Varma (1):
> >   drm/i915/gvt: replace idr_init() by idr_init_base()
> > 
> > Julian Stecklina (1):
> >   drm/i915/gvt: treat intel_gvt_mpt as const in gvt code
> > 
> > Yan Zhao (1):
> >   drm/i915/gvt: correct a false comment of flag F_UNALIGN
> > 
> >  drivers/gpu/drm/i915/gvt/display.c  | 179 
> > 
> >  drivers/gpu/drm/i915/gvt/gtt.c  |  64 +
> >  drivers/gpu/drm/i915/gvt/gtt.h  |   4 +
> >  drivers/gpu/drm/i915/gvt/gvt.c  |  13 ++-
> >  drivers/gpu/drm/i915/gvt/gvt.h  |   7 +-
> >  drivers/gpu/drm/i915/gvt/handlers.c |  44 -
> >  drivers/gpu/drm/i915/gvt/kvmgt.c|   2 +-
> >  drivers/gpu/drm/i915/gvt/mmio.c |   5 +
> >  drivers/gpu/drm/i915/gvt/mmio.h |   4 +
> >  drivers/gpu/drm/i915/gvt/mpt.h  |   2 +-
> >  drivers/gpu/drm/i915/gvt/vgpu.c |   2 +-
> >  drivers/gpu/drm/i915/i915_drv.c |   2 +
> >  drivers/gpu/drm/i915/intel_gvt.c|  15 +++
> >  drivers/gpu/drm/i915/intel_gvt.h|   5 +
> >  14 files changed, 338 insertions(+), 10 deletions(-)
> > 
> > -- 
> > 
> > $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
> ___
> intel-gvt-dev mailing list
> intel-gvt-...@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev

-- 

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


signature.asc
Description: PGP signature
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Joonas Lahtinen]

Quoting Zhenyu Wang (2020-11-23 11:05:17)
> 
> Hi,
> 
> Here's gvt next pull for v5.11. Mostly it's for host suspend/resume
> fix with vGPU active and with some other enhancement as details below.
> Note that this includes some minor i915 driver change to add gvt hook
> in suspend/resume function which has been sent and reviewed on
> intel-gfx list.
> 
> I just generated against drm-intel-next-queued-2020-11-03 which this
> tree bases on now. Let me know if there's any issue in merge.

Sometimes GVT changes are paired with changes related the i915 side
to adjust the running virtual clients. The changes are more often
related to GT side, but there's also been display related changes.

Going forward, would we want to continue to apply gvt-next to
drm-intel-next (-queued is planned to be deprecated) or
should we use drm-intel-gt-next?

Or should we always strictly apply the GVT changes to drm-intel-next,
and then any related i915 changes to drm-intel-next or drm-intel-gt-next
depending on which one they are related to?

Regards, Joonas

> Thanks
> --
> The following changes since commit 139caf7ca2866cd0a45814ff938cb0c33920a266:
> 
>   drm/i915: Update DRIVER_DATE to 20201103 (2020-11-03 14:21:25 +0200)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux tags/gvt-next-2020-11-23
> 
> for you to fetch changes up to 9a3a238b3de97b4210c6de66aa88b2d7021ac086:
> 
>   drm/i915/gvt: treat intel_gvt_mpt as const in gvt code (2020-11-23 17:14:20 
> +0800)
> 
> 
> gvt-next-2020-11-23
> 
> - Fix host suspend/resume with vGPU (Colin)
> - optimize idr init (Varma)
> - Change intel_gvt_mpt as const (Julian)
> - One comment error fix (Yan)
> 
> 
> Colin Xu (3):
>   drm/i915/gvt: Save/restore HW status to support GVT suspend/resume
>   drm/i915: Add GVT resume routine to i915
>   drm/i915/gvt: Fix virtual display setup for BXT/APL
> 
> Deepak R Varma (1):
>   drm/i915/gvt: replace idr_init() by idr_init_base()
> 
> Julian Stecklina (1):
>   drm/i915/gvt: treat intel_gvt_mpt as const in gvt code
> 
> Yan Zhao (1):
>   drm/i915/gvt: correct a false comment of flag F_UNALIGN
> 
>  drivers/gpu/drm/i915/gvt/display.c  | 179 
> 
>  drivers/gpu/drm/i915/gvt/gtt.c  |  64 +
>  drivers/gpu/drm/i915/gvt/gtt.h  |   4 +
>  drivers/gpu/drm/i915/gvt/gvt.c  |  13 ++-
>  drivers/gpu/drm/i915/gvt/gvt.h  |   7 +-
>  drivers/gpu/drm/i915/gvt/handlers.c |  44 -
>  drivers/gpu/drm/i915/gvt/kvmgt.c|   2 +-
>  drivers/gpu/drm/i915/gvt/mmio.c |   5 +
>  drivers/gpu/drm/i915/gvt/mmio.h |   4 +
>  drivers/gpu/drm/i915/gvt/mpt.h  |   2 +-
>  drivers/gpu/drm/i915/gvt/vgpu.c |   2 +-
>  drivers/gpu/drm/i915/i915_drv.c |   2 +
>  drivers/gpu/drm/i915/intel_gvt.c|  15 +++
>  drivers/gpu/drm/i915/intel_gvt.h|   5 +
>  14 files changed, 338 insertions(+), 10 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

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

[Vivi, Rodrigo]

> On Sep 13, 2020, at 7:34 PM, Zhenyu Wang  wrote:
> 
> On 2020.09.11 19:58:25 -0400, Rodrigo Vivi wrote:
>> On Thu, Sep 10, 2020 at 01:37:20PM +0800, Zhenyu Wang wrote:
>>> 
>>> Hi,
>>> 
>>> As we split pull request for 5.10 this time, here's gvt-next pull
>>> for 5.10. For gvt ww lock fix, Zhi would send another pull based
>>> on gem-next.
>>> 
>>> This includes current command access flag cleanup for
>>> handlers which would be used for next refined cmd scan. And also
>>> two more recent fixes on workaround cmd access and MIA reset state.
>>> 
>>> Thanks
>>> --
>>> The following changes since commit ced026e959bec5046afa310d6474e147b6294da2:
>>> 
>>>  drm/i915: Update DRIVER_DATE to 20200824 (2020-08-24 14:26:38 -0400)
>>> 
>>> are available in the Git repository at:
>>> 
>>>  https://github.com/intel/gvt-linux tags/gvt-next-2020-09-10
>> 
>> This is a malformed pull request line which dim doesn't recognize.
>> Could you please regenerate it?
>> 
>> $ cat /tmp/gvt-next/cur/1599868544.259925_1.rdvivi-losangeles\:2\,S | dim 
>> apply-pull drm-intel-next-queued
>> dim: no pull request found
>> 
> 
> Hmm, strange, it pulls fine here when I tried this in local. I just copied in 
> mutt and
> cat /tmp/gvt-next.0910 | ./dim apply-pull drm-intel-next-queued

sorry... it was dim's fault ;)

dim now accepts python3, but a function used on email parser doesn't work in
the same way...

pulled now, thanks

> 
>>> 
>>> for you to fetch changes up to df398e33b8fd3ac28b3c7166de555e38d26e7391:
>>> 
>>>  drm/i915/gvt: Init vreg GUC_STATUS to GS_MIA_IN_RESET (2020-09-10 13:49:05 
>>> +0800)
>>> 
>>> 
>>> gvt-next-2020-09-10
>>> 
>>> - Cleanup command access flag (Yan)
>>> - New workaround cmd access fix (Colin)
>>> - MIA reset state fix (Colin)
>>> 
>>> 
>>> Colin Xu (2):
>>>  drm/i915/gvt: Add F_CMD_ACCESS for some GEN9 SKU WA MMIO access
>>>  drm/i915/gvt: Init vreg GUC_STATUS to GS_MIA_IN_RESET
>>> 
>>> Yan Zhao (4):
>>>  drm/i915/gvt: rename F_IN_CTX flag to F_SR_IN_CTX
>>>  drm/i915/gvt: remove flag F_CMD_ACCESSED
>>>  drm/i915/gvt: add/modify interfaces for flag F_CMD_ACCESS
>>>  drm/i915/gvt: remove F_CMD_ACCESS flag for some registers
>>> 
>>> drivers/gpu/drm/i915/gvt/cmd_parser.c   |  6 ++---
>>> drivers/gpu/drm/i915/gvt/gvt.h  | 44 
>>> +++--
>>> drivers/gpu/drm/i915/gvt/handlers.c | 32 +---
>>> drivers/gpu/drm/i915/gvt/mmio.c |  3 +++
>>> drivers/gpu/drm/i915/gvt/mmio_context.c |  2 +-
>>> 5 files changed, 49 insertions(+), 38 deletions(-)
>>> 
>>> -- 
>>> 
>>> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
>> 
>> 
>> ___
>> intel-gvt-dev mailing list
>> intel-gvt-...@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev
> 
> -- 
> 
> $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

[Zhenyu Wang]

On 2020.09.11 19:58:25 -0400, Rodrigo Vivi wrote:
> On Thu, Sep 10, 2020 at 01:37:20PM +0800, Zhenyu Wang wrote:
> > 
> > Hi,
> > 
> > As we split pull request for 5.10 this time, here's gvt-next pull
> > for 5.10. For gvt ww lock fix, Zhi would send another pull based
> > on gem-next.
> > 
> > This includes current command access flag cleanup for
> > handlers which would be used for next refined cmd scan. And also
> > two more recent fixes on workaround cmd access and MIA reset state.
> > 
> > Thanks
> > --
> > The following changes since commit ced026e959bec5046afa310d6474e147b6294da2:
> > 
> >   drm/i915: Update DRIVER_DATE to 20200824 (2020-08-24 14:26:38 -0400)
> > 
> > are available in the Git repository at:
> > 
> >   https://github.com/intel/gvt-linux tags/gvt-next-2020-09-10
> 
> This is a malformed pull request line which dim doesn't recognize.
> Could you please regenerate it?
> 
> $ cat /tmp/gvt-next/cur/1599868544.259925_1.rdvivi-losangeles\:2\,S | dim 
> apply-pull drm-intel-next-queued
> dim: no pull request found
>

Hmm, strange, it pulls fine here when I tried this in local. I just copied in 
mutt and
 cat /tmp/gvt-next.0910 | ./dim apply-pull drm-intel-next-queued

> > 
> > for you to fetch changes up to df398e33b8fd3ac28b3c7166de555e38d26e7391:
> > 
> >   drm/i915/gvt: Init vreg GUC_STATUS to GS_MIA_IN_RESET (2020-09-10 
> > 13:49:05 +0800)
> > 
> > 
> > gvt-next-2020-09-10
> > 
> > - Cleanup command access flag (Yan)
> > - New workaround cmd access fix (Colin)
> > - MIA reset state fix (Colin)
> > 
> > 
> > Colin Xu (2):
> >   drm/i915/gvt: Add F_CMD_ACCESS for some GEN9 SKU WA MMIO access
> >   drm/i915/gvt: Init vreg GUC_STATUS to GS_MIA_IN_RESET
> > 
> > Yan Zhao (4):
> >   drm/i915/gvt: rename F_IN_CTX flag to F_SR_IN_CTX
> >   drm/i915/gvt: remove flag F_CMD_ACCESSED
> >   drm/i915/gvt: add/modify interfaces for flag F_CMD_ACCESS
> >   drm/i915/gvt: remove F_CMD_ACCESS flag for some registers
> > 
> >  drivers/gpu/drm/i915/gvt/cmd_parser.c   |  6 ++---
> >  drivers/gpu/drm/i915/gvt/gvt.h  | 44 
> > +++--
> >  drivers/gpu/drm/i915/gvt/handlers.c | 32 +---
> >  drivers/gpu/drm/i915/gvt/mmio.c |  3 +++
> >  drivers/gpu/drm/i915/gvt/mmio_context.c |  2 +-
> >  5 files changed, 49 insertions(+), 38 deletions(-)
> > 
> > -- 
> > 
> > $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
> 
> 
> ___
> intel-gvt-dev mailing list
> intel-gvt-...@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev

-- 

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


signature.asc
Description: PGP signature
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Rodrigo Vivi]

On Thu, Sep 10, 2020 at 01:37:20PM +0800, Zhenyu Wang wrote:
> 
> Hi,
> 
> As we split pull request for 5.10 this time, here's gvt-next pull
> for 5.10. For gvt ww lock fix, Zhi would send another pull based
> on gem-next.
> 
> This includes current command access flag cleanup for
> handlers which would be used for next refined cmd scan. And also
> two more recent fixes on workaround cmd access and MIA reset state.
> 
> Thanks
> --
> The following changes since commit ced026e959bec5046afa310d6474e147b6294da2:
> 
>   drm/i915: Update DRIVER_DATE to 20200824 (2020-08-24 14:26:38 -0400)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux tags/gvt-next-2020-09-10

This is a malformed pull request line which dim doesn't recognize.
Could you please regenerate it?

$ cat /tmp/gvt-next/cur/1599868544.259925_1.rdvivi-losangeles\:2\,S | dim 
apply-pull drm-intel-next-queued
dim: no pull request found

> 
> for you to fetch changes up to df398e33b8fd3ac28b3c7166de555e38d26e7391:
> 
>   drm/i915/gvt: Init vreg GUC_STATUS to GS_MIA_IN_RESET (2020-09-10 13:49:05 
> +0800)
> 
> 
> gvt-next-2020-09-10
> 
> - Cleanup command access flag (Yan)
> - New workaround cmd access fix (Colin)
> - MIA reset state fix (Colin)
> 
> 
> Colin Xu (2):
>   drm/i915/gvt: Add F_CMD_ACCESS for some GEN9 SKU WA MMIO access
>   drm/i915/gvt: Init vreg GUC_STATUS to GS_MIA_IN_RESET
> 
> Yan Zhao (4):
>   drm/i915/gvt: rename F_IN_CTX flag to F_SR_IN_CTX
>   drm/i915/gvt: remove flag F_CMD_ACCESSED
>   drm/i915/gvt: add/modify interfaces for flag F_CMD_ACCESS
>   drm/i915/gvt: remove F_CMD_ACCESS flag for some registers
> 
>  drivers/gpu/drm/i915/gvt/cmd_parser.c   |  6 ++---
>  drivers/gpu/drm/i915/gvt/gvt.h  | 44 
> +++--
>  drivers/gpu/drm/i915/gvt/handlers.c | 32 +---
>  drivers/gpu/drm/i915/gvt/mmio.c |  3 +++
>  drivers/gpu/drm/i915/gvt/mmio_context.c |  2 +-
>  5 files changed, 49 insertions(+), 38 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

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

[Jani Nikula]

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

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

[Zhenyu Wang]

On 2020.07.27 16:39:58 +, Vivi, Rodrigo wrote:
> 
> 
> > On Jul 21, 2020, at 5:42 PM, Zhenyu Wang  wrote:
> > 
> > On 2020.07.21 14:04:41 +0300, Joonas Lahtinen wrote:
> >> Quoting Zhenyu Wang (2020-07-20 11:05:41)
> >>> 
> >>> Hi,
> >>> 
> >>> Sorry that this might be a bit late as last week our QA people were
> >>> busy on something else..So this is gvt changes queued for 5.9 which is
> >>> to improve guest suspend/resume with proper PCI PM state tracking for
> >>> resource handling, e.g ppgtt. Hopefully this could still be in queue
> >>> for 5.9.
> >> 
> >> Is this a regression fix to a problem introduced by previous
> >> gvt-next PR targeting 5.9?
> >> 
> >> Or is it an incremental improvement over 5.8?
> >> 
> > 
> > Second case. This is incremental improvement. Guest suspend/resume
> > did work somehow before but has bad performance and possible failure
> > with some guest versions.
> 
> I'm afraid Jani already sent the last pull request towards 5.9.
> So if there are fixes inside this pull request this should move to the 
> -next-fixes
> 
> and the remaining improvements to another 5.10 pull request
> 

Got it. I'll split out those fixes for another pull.

Thanks


signature.asc
Description: PGP signature
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Vivi, Rodrigo]

> On Jul 21, 2020, at 5:42 PM, Zhenyu Wang  wrote:
> 
> On 2020.07.21 14:04:41 +0300, Joonas Lahtinen wrote:
>> Quoting Zhenyu Wang (2020-07-20 11:05:41)
>>> 
>>> Hi,
>>> 
>>> Sorry that this might be a bit late as last week our QA people were
>>> busy on something else..So this is gvt changes queued for 5.9 which is
>>> to improve guest suspend/resume with proper PCI PM state tracking for
>>> resource handling, e.g ppgtt. Hopefully this could still be in queue
>>> for 5.9.
>> 
>> Is this a regression fix to a problem introduced by previous
>> gvt-next PR targeting 5.9?
>> 
>> Or is it an incremental improvement over 5.8?
>> 
> 
> Second case. This is incremental improvement. Guest suspend/resume
> did work somehow before but has bad performance and possible failure
> with some guest versions.

I'm afraid Jani already sent the last pull request towards 5.9.
So if there are fixes inside this pull request this should move to the 
-next-fixes

and the remaining improvements to another 5.10 pull request

Thanks,
Rodrigo.

> 
> Thanks
> 
>> 
>>> 
>>> Thanks
>>> --
>>> The following changes since commit d524b87f77364db096855d7eb714ffacec974ddf:
>>> 
>>>  drm/i915: Update DRIVER_DATE to 20200702 (2020-07-02 21:25:28 +0300)
>>> 
>>> are available in the Git repository at:
>>> 
>>>  https://github.com/intel/gvt-linux tags/gvt-next-2020-07-20
>>> 
>>> for you to fetch changes up to 02b5fc1527c0bb26a1012c6a806dc033f3b125a6:
>>> 
>>>  drm/i915/gvt: Remove intel_vgpu_reset_gtt() since no one use it. 
>>> (2020-07-14 16:42:14 +0800)
>>> 
>>> 
>>> gvt-next-2020-07-20
>>> 
>>> - Improve guest suspend/resume handling (Colin)
>>> 
>>> 
>>> Colin Xu (3):
>>>  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
>>>  drm/i915/gvt: Remove intel_vgpu_reset_gtt() since no one use it.
>>> 
>>> drivers/gpu/drm/i915/gvt/cfg_space.c | 24 
>>> drivers/gpu/drm/i915/gvt/gtt.c   | 20 +---
>>> drivers/gpu/drm/i915/gvt/gtt.h   |  3 ++-
>>> drivers/gpu/drm/i915/gvt/gvt.h   |  3 +++
>>> drivers/gpu/drm/i915/gvt/vgpu.c  | 20 +---
>>> 5 files changed, 47 insertions(+), 23 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

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

[Zhenyu Wang]

On 2020.07.21 14:04:41 +0300, Joonas Lahtinen wrote:
> Quoting Zhenyu Wang (2020-07-20 11:05:41)
> > 
> > Hi,
> > 
> > Sorry that this might be a bit late as last week our QA people were
> > busy on something else..So this is gvt changes queued for 5.9 which is
> > to improve guest suspend/resume with proper PCI PM state tracking for
> > resource handling, e.g ppgtt. Hopefully this could still be in queue
> > for 5.9.
> 
> Is this a regression fix to a problem introduced by previous
> gvt-next PR targeting 5.9?
> 
> Or is it an incremental improvement over 5.8?
>

Second case. This is incremental improvement. Guest suspend/resume
did work somehow before but has bad performance and possible failure
with some guest versions.

Thanks

> 
> > 
> > Thanks
> > --
> > The following changes since commit d524b87f77364db096855d7eb714ffacec974ddf:
> > 
> >   drm/i915: Update DRIVER_DATE to 20200702 (2020-07-02 21:25:28 +0300)
> > 
> > are available in the Git repository at:
> > 
> >   https://github.com/intel/gvt-linux tags/gvt-next-2020-07-20
> > 
> > for you to fetch changes up to 02b5fc1527c0bb26a1012c6a806dc033f3b125a6:
> > 
> >   drm/i915/gvt: Remove intel_vgpu_reset_gtt() since no one use it. 
> > (2020-07-14 16:42:14 +0800)
> > 
> > 
> > gvt-next-2020-07-20
> > 
> > - Improve guest suspend/resume handling (Colin)
> > 
> > 
> > Colin Xu (3):
> >   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
> >   drm/i915/gvt: Remove intel_vgpu_reset_gtt() since no one use it.
> > 
> >  drivers/gpu/drm/i915/gvt/cfg_space.c | 24 
> >  drivers/gpu/drm/i915/gvt/gtt.c   | 20 +---
> >  drivers/gpu/drm/i915/gvt/gtt.h   |  3 ++-
> >  drivers/gpu/drm/i915/gvt/gvt.h   |  3 +++
> >  drivers/gpu/drm/i915/gvt/vgpu.c  | 20 +---
> >  5 files changed, 47 insertions(+), 23 deletions(-)
> > --

-- 
Open Source Technology Center, Intel ltd.

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


signature.asc
Description: PGP signature
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Joonas Lahtinen]

Quoting Zhenyu Wang (2020-07-20 11:05:41)
> 
> Hi,
> 
> Sorry that this might be a bit late as last week our QA people were
> busy on something else..So this is gvt changes queued for 5.9 which is
> to improve guest suspend/resume with proper PCI PM state tracking for
> resource handling, e.g ppgtt. Hopefully this could still be in queue
> for 5.9.

Is this a regression fix to a problem introduced by previous
gvt-next PR targeting 5.9?

Or is it an incremental improvement over 5.8?

Regards, Joonas

> 
> Thanks
> --
> The following changes since commit d524b87f77364db096855d7eb714ffacec974ddf:
> 
>   drm/i915: Update DRIVER_DATE to 20200702 (2020-07-02 21:25:28 +0300)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux tags/gvt-next-2020-07-20
> 
> for you to fetch changes up to 02b5fc1527c0bb26a1012c6a806dc033f3b125a6:
> 
>   drm/i915/gvt: Remove intel_vgpu_reset_gtt() since no one use it. 
> (2020-07-14 16:42:14 +0800)
> 
> 
> gvt-next-2020-07-20
> 
> - Improve guest suspend/resume handling (Colin)
> 
> 
> Colin Xu (3):
>   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
>   drm/i915/gvt: Remove intel_vgpu_reset_gtt() since no one use it.
> 
>  drivers/gpu/drm/i915/gvt/cfg_space.c | 24 
>  drivers/gpu/drm/i915/gvt/gtt.c   | 20 +---
>  drivers/gpu/drm/i915/gvt/gtt.h   |  3 ++-
>  drivers/gpu/drm/i915/gvt/gvt.h   |  3 +++
>  drivers/gpu/drm/i915/gvt/vgpu.c  | 20 +---
>  5 files changed, 47 insertions(+), 23 deletions(-)
> --
___
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

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

[Joonas Lahtinen]

Quoting Zhenyu Wang (2020-05-12 12:40:17)
> 
> Hi,
> 
> This includes support for ppgtt update by LRI command which gvt
> replaces by shadow ppgtt, another small optimization for shadow
> ctx and one workload destroy cleanup.

This is now pulled. Thanks for the PR.

Regards, Joonas

> 
> Thanks
> --
> 
> The following changes since commit fb55c735522352704c35d899d0b253453cf0e799:
> 
>   drm/i915/gvt: skip populate shadow context if guest context not changed 
> (2020-04-17 17:31:22 +0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux tags/gvt-next-2020-05-12
> 
> for you to fetch changes up to 47e51832ae93534d872511ba557115722582d94c:
> 
>   drm/i915/gvt: use context lrc_reg_state for shadow ppgtt override 
> (2020-05-08 12:37:14 +0800)
> 
> 
> gvt-next-2020-05-12
> 
> - Support PPGTT update via LRI cmd (Zhenyu)
> - Remove extra kmap for shadow ctx update (Zhenyu)
> - Move workload cleanup out of execlist handling code (Zhenyu)
> 
> 
> Zhenyu Wang (3):
>   drm/i915/gvt: move workload destroy out of execlist complete
>   drm/i915/gvt: Support PPGTT table load command
>   drm/i915/gvt: use context lrc_reg_state for shadow ppgtt override
> 
>  drivers/gpu/drm/i915/gvt/cmd_parser.c |  45 +
>  drivers/gpu/drm/i915/gvt/execlist.c   |   2 -
>  drivers/gpu/drm/i915/gvt/gtt.c|   1 +
>  drivers/gpu/drm/i915/gvt/gtt.h|   1 +
>  drivers/gpu/drm/i915/gvt/handlers.c   |   2 +-
>  drivers/gpu/drm/i915/gvt/scheduler.c  | 115 
> +++---
>  drivers/gpu/drm/i915/gvt/scheduler.h  |   1 +
>  7 files changed, 155 insertions(+), 12 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

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

[Joonas Lahtinen]

Quoting Zhenyu Wang (2020-04-26 05:46:19)
> On 2020.04.22 13:12:30 +0800, Zhenyu Wang wrote:
> > 
> > Hi,
> > 
> > Here's current gvt-next. This removes left non-upstream xen support bits
> > which will be kept out of tree instead. And several guest context shadow
> > optimizations from Yan.
> > 
> > Thanks
> > --
> 
> Ping for merge..

Pulled now. Thanks for the PR.

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

[Zhenyu Wang]

On 2020.04.22 13:12:30 +0800, Zhenyu Wang wrote:
> 
> Hi,
> 
> Here's current gvt-next. This removes left non-upstream xen support bits
> which will be kept out of tree instead. And several guest context shadow
> optimizations from Yan.
> 
> Thanks
> --

Ping for merge..

> 
> 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 tags/gvt-next-2020-04-22
> 
> for you to fetch changes up to fb55c735522352704c35d899d0b253453cf0e799:
> 
>   drm/i915/gvt: skip populate shadow context if guest context not changed 
> (2020-04-17 17:31:22 +0800)
> 
> 
> gvt-next-2020-04-22
> 
> - remove non-upstream xen support bits (Christoph)
> - guest context shadow copy optimization (Yan)
> - guest context tracking for shadow skip optimization (Yan)
> 
> 
> Christoph Hellwig (1):
>   i915/gvt: remove unused xen bits
> 
> Yan Zhao (3):
>   drm/i915/gvt: access shadow ctx via its virtual address directly
>   drm/i915/gvt: combine access to consecutive guest context pages
>   drm/i915/gvt: skip populate shadow context if guest context not changed
> 
>  drivers/gpu/drm/i915/gvt/gtt.c   |  15 +
>  drivers/gpu/drm/i915/gvt/gvt.c   |   1 -
>  drivers/gpu/drm/i915/gvt/gvt.h   |   5 ++
>  drivers/gpu/drm/i915/gvt/hypercall.h |   2 -
>  drivers/gpu/drm/i915/gvt/scheduler.c | 127 
> ++-
>  5 files changed, 114 insertions(+), 36 deletions(-)
> 
> -- 
> Open Source Technology Center, Intel ltd.
> 
> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827



> ___
> intel-gvt-dev mailing list
> intel-gvt-...@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


signature.asc
Description: PGP signature
___
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]

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 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


signature.asc
Description: PGP signature
___
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  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]

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


signature.asc
Description: PGP signature
___
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-...@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]

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-...@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


signature.asc
Description: PGP signature
___
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

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

[Rodrigo Vivi]

On Tue, Mar 10, 2020 at 04:19:28PM +0800, Zhenyu Wang wrote:
> 
> Hi,
> 
> Here's more gvt change for -next. Mostly rebase and fix Chris's
> cleanup on intel engine and dev_priv usage. And also one fix for CFL
> after VFIO edid enabled in last gvt-next pull.

pulled to dinq,

Thanks,
Rodrigo.

> 
> thanks
> --
> The following changes since commit a8bb49b64c4f4284fb36169bdd9fc6efd62eb26a:
> 
>   drm/i915/gvt: Fix drm_WARN issue where vgpu ptr is unavailable (2020-02-25 
> 16:13:04 +0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux tags/gvt-next-2020-03-10
> 
> for you to fetch changes up to a61ac1e75105a077ec1efd6923ae3c619f862304:
> 
>   drm/i915/gvt: Wean gvt off using dev_priv (2020-03-06 10:08:10 +0800)
> 
> 
> gvt-next-2020-03-10
> 
> - Fix CFL dmabuf display after vfio edid enabling (Tina)
> - Clean up scan non-priv batch debugfs entry (Chris)
> - Use intel engines initialized in gvt, cleanup previous ring id (Chris)
> - Use intel_gt instead (Chris)
> 
> 
> Chris Wilson (3):
>   drm/i915/gvt: cleanup debugfs scan_nonprivbb
>   drm/i915/gvt: Wean gvt off dev_priv->engine[]
>   drm/i915/gvt: Wean gvt off using dev_priv
> 
> Tina Zhang (1):
>   drm/i915/gvt: Fix dma-buf display blur issue on CFL
> 
>  drivers/gpu/drm/i915/gvt/aperture_gm.c  |  84 ++-
>  drivers/gpu/drm/i915/gvt/cfg_space.c|   8 +-
>  drivers/gpu/drm/i915/gvt/cmd_parser.c   | 204 --
>  drivers/gpu/drm/i915/gvt/debugfs.c  |  45 +-
>  drivers/gpu/drm/i915/gvt/display.c  |  21 +--
>  drivers/gpu/drm/i915/gvt/dmabuf.c   |   4 +-
>  drivers/gpu/drm/i915/gvt/edid.c |  16 +-
>  drivers/gpu/drm/i915/gvt/execlist.c | 103 +++--
>  drivers/gpu/drm/i915/gvt/execlist.h |   5 +-
>  drivers/gpu/drm/i915/gvt/fb_decoder.c   |   6 +-
>  drivers/gpu/drm/i915/gvt/firmware.c |  16 +-
>  drivers/gpu/drm/i915/gvt/gtt.c  |  50 +++
>  drivers/gpu/drm/i915/gvt/gvt.c  |  38 ++---
>  drivers/gpu/drm/i915/gvt/gvt.h  |  25 ++--
>  drivers/gpu/drm/i915/gvt/handlers.c | 193 -
>  drivers/gpu/drm/i915/gvt/interrupt.c|  14 +-
>  drivers/gpu/drm/i915/gvt/kvmgt.c|  10 +-
>  drivers/gpu/drm/i915/gvt/mmio.c |   6 +-
>  drivers/gpu/drm/i915/gvt/mmio.h |   4 +-
>  drivers/gpu/drm/i915/gvt/mmio_context.c | 127 
>  drivers/gpu/drm/i915/gvt/mmio_context.h |   5 +-
>  drivers/gpu/drm/i915/gvt/sched_policy.c |  25 ++--
>  drivers/gpu/drm/i915/gvt/scheduler.c| 249 
> +++-
>  drivers/gpu/drm/i915/gvt/scheduler.h|   9 +-
>  drivers/gpu/drm/i915/gvt/vgpu.c |  12 +-
>  25 files changed, 601 insertions(+), 678 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

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

[Zhenyu Wang]

On 2020.02.26 13:58:32 +0200, Jani Nikula wrote:
> On Wed, 26 Feb 2020, Zhenyu Wang  wrote:
> > Hi,
> >
> > Here's gvt-next pull. Mostly for cleanup and kvmgt specific struct
> > has been moved to its own module, also enable VFIO edid for all platform
> > including CML. Pls see details below.
> 
> What happened with [1]? Would've liked to see that moving forward.
> 
> 
> [1] 
> http://patchwork.freedesktop.org/patch/msgid/20200117153554.3104278-1-ch...@chris-wilson.co.uk
>

I just pinged Zhuocheng for who I asked to help on verifying that, but
looks still have problem to bring up and there're more warnings.. We'll
try to resolve it asap. Sorry for the delay.


> >
> > Thanks
> > --
> > The following changes since commit e24bcd34c1dd7dabde4a8546920537f7137e3c5f:
> >
> >   drm/i915/dp: Add all tiled and port sync conns to modeset (2020-02-20 
> > 13:55:02 +0530)
> >
> > are available in the Git repository at:
> >
> >   https://github.com/intel/gvt-linux tags/gvt-next-2020-02-26
> >
> > for you to fetch changes up to a8bb49b64c4f4284fb36169bdd9fc6efd62eb26a:
> >
> >   drm/i915/gvt: Fix drm_WARN issue where vgpu ptr is unavailable 
> > (2020-02-25 16:13:04 +0800)
> >
> > 
> > gvt-next-2020-02-26
> >
> > - Enable VFIO edid for all platform (Zhenyu)
> > - Code cleanup for attr group and unused vblank complete (Zhenyu, Julian)
> > - Make gvt oblivious of kvmgt data structures (Julian)
> > - Make WARN* drm specific (Pankaj)
> >
> > 
> > Julian Stecklina (2):
> >   drm/i915/gvt: remove unused vblank_done completion
> >   drm/i915/gvt: make gvt oblivious of kvmgt data structures
> >
> > Pankaj Bharadiya (2):
> >   drm/i915/gvt: Make WARN* drm specific where drm_priv ptr is available
> >   drm/i915/gvt: Make WARN* drm specific where vgpu ptr is available
> >
> > Tina Zhang (1):
> >   drm/i915/gvt: Fix drm_WARN issue where vgpu ptr is unavailable
> >
> > Zhenyu Wang (3):
> >   drm/i915/gvt: remove unused type attributes
> >   drm/i915/gvt: Enable vfio edid for all GVT supported platform
> >   Merge drm-intel-next-queued into gvt-next
> >
> >  drivers/gpu/drm/i915/gvt/aperture_gm.c  |   6 +-
> >  drivers/gpu/drm/i915/gvt/cfg_space.c|  23 ++-
> >  drivers/gpu/drm/i915/gvt/cmd_parser.c   |   4 +-
> >  drivers/gpu/drm/i915/gvt/display.c  |   6 +-
> >  drivers/gpu/drm/i915/gvt/dmabuf.c   |   4 +-
> >  drivers/gpu/drm/i915/gvt/edid.c |  19 +-
> >  drivers/gpu/drm/i915/gvt/gtt.c  |  21 ++-
> >  drivers/gpu/drm/i915/gvt/gvt.c  |   8 +-
> >  drivers/gpu/drm/i915/gvt/gvt.h  |  37 +---
> >  drivers/gpu/drm/i915/gvt/handlers.c |  22 ++-
> >  drivers/gpu/drm/i915/gvt/interrupt.c|  15 +-
> >  drivers/gpu/drm/i915/gvt/kvmgt.c| 303 
> > +++-
> >  drivers/gpu/drm/i915/gvt/mmio.c |  30 ++--
> >  drivers/gpu/drm/i915/gvt/mmio_context.c |   6 +-
> >  drivers/gpu/drm/i915/gvt/scheduler.c|   6 +-
> >  drivers/gpu/drm/i915/gvt/vgpu.c |  10 +-
> >  16 files changed, 304 insertions(+), 216 deletions(-)
> 
> -- 
> Jani Nikula, Intel Open Source Graphics Center

-- 
Open Source Technology Center, Intel ltd.

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


signature.asc
Description: PGP signature
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Rodrigo Vivi]

On Wed, Feb 26, 2020 at 06:38:40PM +0800, Zhenyu Wang wrote:
> 
> Hi,
> 
> Here's gvt-next pull. Mostly for cleanup and kvmgt specific struct
> has been moved to its own module, also enable VFIO edid for all platform
> including CML. Pls see details below.

pulled, thanks

> 
> Thanks
> --
> The following changes since commit e24bcd34c1dd7dabde4a8546920537f7137e3c5f:
> 
>   drm/i915/dp: Add all tiled and port sync conns to modeset (2020-02-20 
> 13:55:02 +0530)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux tags/gvt-next-2020-02-26
> 
> for you to fetch changes up to a8bb49b64c4f4284fb36169bdd9fc6efd62eb26a:
> 
>   drm/i915/gvt: Fix drm_WARN issue where vgpu ptr is unavailable (2020-02-25 
> 16:13:04 +0800)
> 
> 
> gvt-next-2020-02-26
> 
> - Enable VFIO edid for all platform (Zhenyu)
> - Code cleanup for attr group and unused vblank complete (Zhenyu, Julian)
> - Make gvt oblivious of kvmgt data structures (Julian)
> - Make WARN* drm specific (Pankaj)
> 
> 
> Julian Stecklina (2):
>   drm/i915/gvt: remove unused vblank_done completion
>   drm/i915/gvt: make gvt oblivious of kvmgt data structures
> 
> Pankaj Bharadiya (2):
>   drm/i915/gvt: Make WARN* drm specific where drm_priv ptr is available
>   drm/i915/gvt: Make WARN* drm specific where vgpu ptr is available
> 
> Tina Zhang (1):
>   drm/i915/gvt: Fix drm_WARN issue where vgpu ptr is unavailable
> 
> Zhenyu Wang (3):
>   drm/i915/gvt: remove unused type attributes
>   drm/i915/gvt: Enable vfio edid for all GVT supported platform
>   Merge drm-intel-next-queued into gvt-next
> 
>  drivers/gpu/drm/i915/gvt/aperture_gm.c  |   6 +-
>  drivers/gpu/drm/i915/gvt/cfg_space.c|  23 ++-
>  drivers/gpu/drm/i915/gvt/cmd_parser.c   |   4 +-
>  drivers/gpu/drm/i915/gvt/display.c  |   6 +-
>  drivers/gpu/drm/i915/gvt/dmabuf.c   |   4 +-
>  drivers/gpu/drm/i915/gvt/edid.c |  19 +-
>  drivers/gpu/drm/i915/gvt/gtt.c  |  21 ++-
>  drivers/gpu/drm/i915/gvt/gvt.c  |   8 +-
>  drivers/gpu/drm/i915/gvt/gvt.h  |  37 +---
>  drivers/gpu/drm/i915/gvt/handlers.c |  22 ++-
>  drivers/gpu/drm/i915/gvt/interrupt.c|  15 +-
>  drivers/gpu/drm/i915/gvt/kvmgt.c| 303 
> +++-
>  drivers/gpu/drm/i915/gvt/mmio.c |  30 ++--
>  drivers/gpu/drm/i915/gvt/mmio_context.c |   6 +-
>  drivers/gpu/drm/i915/gvt/scheduler.c|   6 +-
>  drivers/gpu/drm/i915/gvt/vgpu.c |  10 +-
>  16 files changed, 304 insertions(+), 216 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

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

[Jani Nikula]

On Wed, 26 Feb 2020, Zhenyu Wang  wrote:
> Hi,
>
> Here's gvt-next pull. Mostly for cleanup and kvmgt specific struct
> has been moved to its own module, also enable VFIO edid for all platform
> including CML. Pls see details below.

What happened with [1]? Would've liked to see that moving forward.

BR,
Jani.


[1] 
http://patchwork.freedesktop.org/patch/msgid/20200117153554.3104278-1-ch...@chris-wilson.co.uk

>
> Thanks
> --
> The following changes since commit e24bcd34c1dd7dabde4a8546920537f7137e3c5f:
>
>   drm/i915/dp: Add all tiled and port sync conns to modeset (2020-02-20 
> 13:55:02 +0530)
>
> are available in the Git repository at:
>
>   https://github.com/intel/gvt-linux tags/gvt-next-2020-02-26
>
> for you to fetch changes up to a8bb49b64c4f4284fb36169bdd9fc6efd62eb26a:
>
>   drm/i915/gvt: Fix drm_WARN issue where vgpu ptr is unavailable (2020-02-25 
> 16:13:04 +0800)
>
> 
> gvt-next-2020-02-26
>
> - Enable VFIO edid for all platform (Zhenyu)
> - Code cleanup for attr group and unused vblank complete (Zhenyu, Julian)
> - Make gvt oblivious of kvmgt data structures (Julian)
> - Make WARN* drm specific (Pankaj)
>
> 
> Julian Stecklina (2):
>   drm/i915/gvt: remove unused vblank_done completion
>   drm/i915/gvt: make gvt oblivious of kvmgt data structures
>
> Pankaj Bharadiya (2):
>   drm/i915/gvt: Make WARN* drm specific where drm_priv ptr is available
>   drm/i915/gvt: Make WARN* drm specific where vgpu ptr is available
>
> Tina Zhang (1):
>   drm/i915/gvt: Fix drm_WARN issue where vgpu ptr is unavailable
>
> Zhenyu Wang (3):
>   drm/i915/gvt: remove unused type attributes
>   drm/i915/gvt: Enable vfio edid for all GVT supported platform
>   Merge drm-intel-next-queued into gvt-next
>
>  drivers/gpu/drm/i915/gvt/aperture_gm.c  |   6 +-
>  drivers/gpu/drm/i915/gvt/cfg_space.c|  23 ++-
>  drivers/gpu/drm/i915/gvt/cmd_parser.c   |   4 +-
>  drivers/gpu/drm/i915/gvt/display.c  |   6 +-
>  drivers/gpu/drm/i915/gvt/dmabuf.c   |   4 +-
>  drivers/gpu/drm/i915/gvt/edid.c |  19 +-
>  drivers/gpu/drm/i915/gvt/gtt.c  |  21 ++-
>  drivers/gpu/drm/i915/gvt/gvt.c  |   8 +-
>  drivers/gpu/drm/i915/gvt/gvt.h  |  37 +---
>  drivers/gpu/drm/i915/gvt/handlers.c |  22 ++-
>  drivers/gpu/drm/i915/gvt/interrupt.c|  15 +-
>  drivers/gpu/drm/i915/gvt/kvmgt.c| 303 
> +++-
>  drivers/gpu/drm/i915/gvt/mmio.c |  30 ++--
>  drivers/gpu/drm/i915/gvt/mmio_context.c |   6 +-
>  drivers/gpu/drm/i915/gvt/scheduler.c|   6 +-
>  drivers/gpu/drm/i915/gvt/vgpu.c |  10 +-
>  16 files changed, 304 insertions(+), 216 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

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

[Zhenyu Wang]

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


signature.asc
Description: PGP signature
___
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]

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-...@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


signature.asc
Description: PGP signature
___
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

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

[Vetter, Daniel]

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,
> > > > 
> > > > 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 (2019-05-13 13:53:35 +0300)
> > > > 
> > > > are available in the Git repository at:
> > > > 
> > > >   https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-
> > > > 2019-
> > > > 09-06
> > > > 
> > > > for you to fetch changes up to
> > > > 4a5322560aa235efa84c0aa34c00e5749a0792fd:
> > > > 
> > > >   drm/i915/gvt: update RING_START reg of vGPU when the context
> > > > is
> > > > submitted to i915 (2019-09-06 13:39:09 +0800)
> > > 
> > > $ dim pull-request-next-fixes
> > > Using drm/drm-next as the upstream
> > > dim: 4a5322560aa2 ("drm/i915/gvt: update RING_START reg of vGPU
> > > when
> > > the context is submitted to i915"): Link tag missing.
> > > dim: 0a3242bdb477 ("drm/i915/gvt: update vgpu workload head
> > > pointer
> > > correctly"): Link tag missing.
> > > dim: ERROR: issues in commits detected, aborting
> > > 
> > > I wonder how I should proceed here. In the past I was always
> > > bypasssing dim,
> > > but now that drm maintainers also use dim I'm sure this will blow
> > > up
> > > there anyways.
> > > 
> > > But gvt patches are not tracked on our CI individually hence they
> > > don't
> > > have Links.
> > > 
> > > Jani, Joonas, how are you guys handling this?
> > > 
> > > Daniel, Dave, ideas?
> > 
> > dim doesn't require Link: tags yet for pull requests (because most
> > drm
> > trees aren't managed by dim and so lack them).
> 
> I'm confused now.
> 
> function dim_pull_request
> calls
> checkpatch_commit_push_range 1 "$upstream..$branch"
> (except for drm-intel-next)
> 
> and checkpatch_commit_push checks for the link.
> 
> So if you also use dim for your pull request I'm wondering how you
> are not getting that

On the push side we set dim_managed_branch (or whatever it's called) to
1, on the pull side it's side 0. That disables certain checks like the
Link: tag check. Also push should only check commits authored by you,
so this is only really an issue with cherry-picks.

That was at least the idea behind all this, maybe it stopped working.
-Daniel

> 
> In the past whenever I had this problem on dinf I commented out the
> link check but end up never coming back to solve the problem
> properly.
> I just wondering that now that dim is in use on drm level if I bypass
> here it becomes a problem for you.
> 
> thoughts?
> 
> > Until we change that,
> > with some doc patches and proper bikeshed on dri-devel I think it's
> > fine if gvt is missing them. At least from a drm.git pov.
> > 
> > What you guys want to do for drm-intel.git is entirely up to you.
> > -Daniel
> > > Thanks,
> > > Rodrigo.
> > > 
> > > > -
> > > > ---
> > > > gvt-next-fixes-2019-09-06
> > > > 
> > > > - Fix guest context head pointer update for hang (Xiaolin)
> > > > - Fix guest context ring state for reset (Weinan)
> > > > 
> > > > -
> > > > ---
> > > > Weinan Li (1):
> > > >   drm/i915/gvt: update RING_START reg of vGPU when the
> > > > context
> > > > is submitted to i915
> > > > 
> > > > Xiaolin Zhang (1):
> > > >   drm/i915/gvt: update vgpu workload head pointer correctly
> > > > 
> > > >  drivers/gpu/drm/i915/gvt/scheduler.c | 45
> > > > +---
> > > >  1 file changed, 32 insertions(+), 13 deletions(-)
> > > > 
> > > > 
> > > > -- 
> > > > Open Source Technology Center, Intel ltd.
> > > > 
> > > > $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
Intel Semiconductor AG
Registered No. 020.30.913.786-7
Registered Office: Badenerstrasse 549, 8048 Zurich, Switzerland
___
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]

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,
> > > > 
> > > > 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 (2019-05-13 13:53:35 +0300)
> > > > 
> > > > are available in the Git repository at:
> > > > 
> > > >   https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2019-
> > > > 09-06
> > > > 
> > > > for you to fetch changes up to
> > > > 4a5322560aa235efa84c0aa34c00e5749a0792fd:
> > > > 
> > > >   drm/i915/gvt: update RING_START reg of vGPU when the context is
> > > > submitted to i915 (2019-09-06 13:39:09 +0800)
> > > 
> > > $ dim pull-request-next-fixes
> > > Using drm/drm-next as the upstream
> > > dim: 4a5322560aa2 ("drm/i915/gvt: update RING_START reg of vGPU when
> > > the context is submitted to i915"): Link tag missing.
> > > dim: 0a3242bdb477 ("drm/i915/gvt: update vgpu workload head pointer
> > > correctly"): Link tag missing.
> > > dim: ERROR: issues in commits detected, aborting
> > > 
> > > I wonder how I should proceed here. In the past I was always
> > > bypasssing dim,
> > > but now that drm maintainers also use dim I'm sure this will blow up
> > > there anyways.
> > > 
> > > But gvt patches are not tracked on our CI individually hence they
> > > don't
> > > have Links.
> > > 
> > > Jani, Joonas, how are you guys handling this?
> > > 
> > > Daniel, Dave, ideas?
> > 
> > dim doesn't require Link: tags yet for pull requests (because most drm
> > trees aren't managed by dim and so lack them).
> 
> I'm confused now.
> 
> function dim_pull_request
> calls
> checkpatch_commit_push_range 1 "$upstream..$branch"
> (except for drm-intel-next)
> 
> and checkpatch_commit_push checks for the link.
> 
> So if you also use dim for your pull request I'm wondering how you
> are not getting that
> 
> In the past whenever I had this problem on dinf I commented out the
> link check but end up never coming back to solve the problem properly.
> I just wondering that now that dim is in use on drm level if I bypass
> here it becomes a problem for you.
> 
> thoughts?

Although gvt is not fully in CI yet, we do have patchwork that I can
add Link: tag, that should be easy for you. Sorry that I wasn't awared
it's required for dim.

> 
> > Until we change that,
> > with some doc patches and proper bikeshed on dri-devel I think it's
> > fine if gvt is missing them. At least from a drm.git pov.
> > 
> > What you guys want to do for drm-intel.git is entirely up to you.
> > -Daniel
> > > 
> > > Thanks,
> > > Rodrigo.
> > > 
> > > > 
> > > > gvt-next-fixes-2019-09-06
> > > > 
> > > > - Fix guest context head pointer update for hang (Xiaolin)
> > > > - Fix guest context ring state for reset (Weinan)
> > > > 
> > > > 
> > > > Weinan Li (1):
> > > >   drm/i915/gvt: update RING_START reg of vGPU when the context
> > > > is submitted to i915
> > > > 
> > > > Xiaolin Zhang (1):
> > > >   drm/i915/gvt: update vgpu workload head pointer correctly
> > > > 
> > > >  drivers/gpu/drm/i915/gvt/scheduler.c | 45
> > > > +---
> > > >  1 file changed, 32 insertions(+), 13 deletions(-)
> > > > 
> > > > 
> > > > -- 
> > > > Open Source Technology Center, Intel ltd.
> > > > 
> > > > $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
> > > 
> > > 
> ___
> intel-gvt-dev mailing list
> intel-gvt-...@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


signature.asc
Description: PGP signature
___
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, 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 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 (2019-05-13 13:53:35 +0300)
> > > 
> > > are available in the Git repository at:
> > > 
> > >   https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2019-
> > > 09-06
> > > 
> > > for you to fetch changes up to
> > > 4a5322560aa235efa84c0aa34c00e5749a0792fd:
> > > 
> > >   drm/i915/gvt: update RING_START reg of vGPU when the context is
> > > submitted to i915 (2019-09-06 13:39:09 +0800)
> > 
> > $ dim pull-request-next-fixes
> > Using drm/drm-next as the upstream
> > dim: 4a5322560aa2 ("drm/i915/gvt: update RING_START reg of vGPU when
> > the context is submitted to i915"): Link tag missing.
> > dim: 0a3242bdb477 ("drm/i915/gvt: update vgpu workload head pointer
> > correctly"): Link tag missing.
> > dim: ERROR: issues in commits detected, aborting
> > 
> > I wonder how I should proceed here. In the past I was always
> > bypasssing dim,
> > but now that drm maintainers also use dim I'm sure this will blow up
> > there anyways.
> > 
> > But gvt patches are not tracked on our CI individually hence they
> > don't
> > have Links.
> > 
> > Jani, Joonas, how are you guys handling this?
> > 
> > Daniel, Dave, ideas?
> 
> dim doesn't require Link: tags yet for pull requests (because most drm
> trees aren't managed by dim and so lack them).

I'm confused now.

function dim_pull_request
calls
checkpatch_commit_push_range 1 "$upstream..$branch"
(except for drm-intel-next)

and checkpatch_commit_push checks for the link.

So if you also use dim for your pull request I'm wondering how you
are not getting that

In the past whenever I had this problem on dinf I commented out the
link check but end up never coming back to solve the problem properly.
I just wondering that now that dim is in use on drm level if I bypass
here it becomes a problem for you.

thoughts?

> Until we change that,
> with some doc patches and proper bikeshed on dri-devel I think it's
> fine if gvt is missing them. At least from a drm.git pov.
> 
> What you guys want to do for drm-intel.git is entirely up to you.
> -Daniel
> > 
> > Thanks,
> > Rodrigo.
> > 
> > > 
> > > gvt-next-fixes-2019-09-06
> > > 
> > > - Fix guest context head pointer update for hang (Xiaolin)
> > > - Fix guest context ring state for reset (Weinan)
> > > 
> > > 
> > > Weinan Li (1):
> > >   drm/i915/gvt: update RING_START reg of vGPU when the context
> > > is submitted to i915
> > > 
> > > Xiaolin Zhang (1):
> > >   drm/i915/gvt: update vgpu workload head pointer correctly
> > > 
> > >  drivers/gpu/drm/i915/gvt/scheduler.c | 45
> > > +---
> > >  1 file changed, 32 insertions(+), 13 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

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

[Vetter, Daniel]

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.
> > --
> > The following changes since commit
> > c36beba6b296b3c05a0f29753b04775e5ae23886:
> > 
> >   drm/i915: Seal races between async GPU cancellation, retirement
> > and signaling (2019-05-13 13:53:35 +0300)
> > 
> > are available in the Git repository at:
> > 
> >   https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2019-
> > 09-06
> > 
> > for you to fetch changes up to
> > 4a5322560aa235efa84c0aa34c00e5749a0792fd:
> > 
> >   drm/i915/gvt: update RING_START reg of vGPU when the context is
> > submitted to i915 (2019-09-06 13:39:09 +0800)
> 
> $ dim pull-request-next-fixes
> Using drm/drm-next as the upstream
> dim: 4a5322560aa2 ("drm/i915/gvt: update RING_START reg of vGPU when
> the context is submitted to i915"): Link tag missing.
> dim: 0a3242bdb477 ("drm/i915/gvt: update vgpu workload head pointer
> correctly"): Link tag missing.
> dim: ERROR: issues in commits detected, aborting
> 
> I wonder how I should proceed here. In the past I was always
> bypasssing dim,
> but now that drm maintainers also use dim I'm sure this will blow up
> there anyways.
> 
> But gvt patches are not tracked on our CI individually hence they
> don't
> have Links.
> 
> Jani, Joonas, how are you guys handling this?
> 
> Daniel, Dave, ideas?

dim doesn't require Link: tags yet for pull requests (because most drm
trees aren't managed by dim and so lack them). Until we change that,
with some doc patches and proper bikeshed on dri-devel I think it's
fine if gvt is missing them. At least from a drm.git pov.

What you guys want to do for drm-intel.git is entirely up to you.
-Daniel
> 
> Thanks,
> Rodrigo.
> 
> > 
> > gvt-next-fixes-2019-09-06
> > 
> > - Fix guest context head pointer update for hang (Xiaolin)
> > - Fix guest context ring state for reset (Weinan)
> > 
> > 
> > Weinan Li (1):
> >   drm/i915/gvt: update RING_START reg of vGPU when the context
> > is submitted to i915
> > 
> > Xiaolin Zhang (1):
> >   drm/i915/gvt: update vgpu workload head pointer correctly
> > 
> >  drivers/gpu/drm/i915/gvt/scheduler.c | 45
> > +---
> >  1 file changed, 32 insertions(+), 13 deletions(-)
> > 
> > 
> > -- 
> > Open Source Technology Center, Intel ltd.
> > 
> > $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
> 
> 
Intel Semiconductor AG
Registered No. 020.30.913.786-7
Registered Office: Badenerstrasse 549, 8048 Zurich, Switzerland
___
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]

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:
> 
>   drm/i915: Seal races between async GPU cancellation, retirement and 
> signaling (2019-05-13 13:53:35 +0300)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2019-09-06
> 
> for you to fetch changes up to 4a5322560aa235efa84c0aa34c00e5749a0792fd:
> 
>   drm/i915/gvt: update RING_START reg of vGPU when the context is submitted 
> to i915 (2019-09-06 13:39:09 +0800)


$ dim pull-request-next-fixes
Using drm/drm-next as the upstream
dim: 4a5322560aa2 ("drm/i915/gvt: update RING_START reg of vGPU when the 
context is submitted to i915"): Link tag missing.
dim: 0a3242bdb477 ("drm/i915/gvt: update vgpu workload head pointer 
correctly"): Link tag missing.
dim: ERROR: issues in commits detected, aborting

I wonder how I should proceed here. In the past I was always bypasssing dim,
but now that drm maintainers also use dim I'm sure this will blow up
there anyways.

But gvt patches are not tracked on our CI individually hence they don't
have Links.

Jani, Joonas, how are you guys handling this?

Daniel, Dave, ideas?

Thanks,
Rodrigo.

> 
> 
> gvt-next-fixes-2019-09-06
> 
> - Fix guest context head pointer update for hang (Xiaolin)
> - Fix guest context ring state for reset (Weinan)
> 
> 
> Weinan Li (1):
>   drm/i915/gvt: update RING_START reg of vGPU when the context is 
> submitted to i915
> 
> Xiaolin Zhang (1):
>   drm/i915/gvt: update vgpu workload head pointer correctly
> 
>  drivers/gpu/drm/i915/gvt/scheduler.c | 45 
> +---
>  1 file changed, 32 insertions(+), 13 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

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

[Rodrigo Vivi]

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:
> 
>   drm/i915: Seal races between async GPU cancellation, retirement and 
> signaling (2019-05-13 13:53:35 +0300)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2019-09-06

pulled, thanks

> 
> for you to fetch changes up to 4a5322560aa235efa84c0aa34c00e5749a0792fd:
> 
>   drm/i915/gvt: update RING_START reg of vGPU when the context is submitted 
> to i915 (2019-09-06 13:39:09 +0800)
> 
> 
> gvt-next-fixes-2019-09-06
> 
> - Fix guest context head pointer update for hang (Xiaolin)
> - Fix guest context ring state for reset (Weinan)
> 
> 
> Weinan Li (1):
>   drm/i915/gvt: update RING_START reg of vGPU when the context is 
> submitted to i915
> 
> Xiaolin Zhang (1):
>   drm/i915/gvt: update vgpu workload head pointer correctly
> 
>  drivers/gpu/drm/i915/gvt/scheduler.c | 45 
> +---
>  1 file changed, 32 insertions(+), 13 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

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

[Rodrigo Vivi]

On Tue, Aug 13, 2019 at 06:06:04PM +0800, Zhenyu Wang wrote:
> 
> Hi,
> 
> Here's gvt-next stuff for next kernel which include several enhancement
> for cmd parser and batch buffer shadow, remove extra debugfs function
> return check, and with other misc changes like typo, static check fix,
> etc.

Pulled, Thanks

> 
> Thanks
> --
> The following changes since commit e0e712fe42ef67bdf45fc348767d1d0a4eeba77f:
> 
>   drm/i915: Update DRIVER_DATE to 20190730 (2019-07-30 11:50:24 -0700)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-2019-08-13
> 
> for you to fetch changes up to 220b65d8009dff397a112ee560c297299ba5e423:
> 
>   drm/i915/gvt: Double check batch buffer size after copy (2019-08-13 
> 17:55:06 +0800)
> 
> 
> gvt-next-2019-08-13
> 
> - Enhance command parser for extra length check (Fred)
> - remove debugfs function return check (Greg)
> - batch buffer end double check after shadow copy (Tina)
> - one typo fix (Zhenyu)
> - klocwork warning fix (Zhi)
> - use struct_size() helper (Gustavo)
> 
> 
> Gao, Fred (3):
>   drm/i915/gvt: Utility for valid command length check
>   drm/i915/gvt: Add MI command valid length check
>   drm/i915/gvt: Add valid length check for MI variable commands
> 
> Greg Kroah-Hartman (1):
>   drm/i915/gvt: no need to check return value of debugfs_create functions
> 
> Gustavo A. R. Silva (1):
>   drm/i915/kvmgt: Use struct_size() helper
> 
> Tina Zhang (1):
>   drm/i915/gvt: Double check batch buffer size after copy
> 
> Zhenyu Wang (1):
>   drm/i915/gvt: Fix typo of VBLANK_TIMER_PERIOD
> 
> Zhi Wang (1):
>   drm/i915/gvt: factor out tlb and mocs register offset table
> 
>  drivers/gpu/drm/i915/gvt/cmd_parser.c   | 180 
> ++--
>  drivers/gpu/drm/i915/gvt/debugfs.c  |  47 ++---
>  drivers/gpu/drm/i915/gvt/gvt.c  |   4 +-
>  drivers/gpu/drm/i915/gvt/gvt.h  |   8 +-
>  drivers/gpu/drm/i915/gvt/interrupt.c|   4 +-
>  drivers/gpu/drm/i915/gvt/kvmgt.c|  15 +--
>  drivers/gpu/drm/i915/gvt/mmio_context.c |  57 ++
>  drivers/gpu/drm/i915/gvt/vgpu.c |   4 +-
>  8 files changed, 212 insertions(+), 107 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

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

[Joonas Lahtinen]

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 warning/error fixes.
> 
> Thanks
> --
> The following changes since commit 447811a686e8da7325516a78069ccfbd139ef1a7:
> 
>   drm/i915/icl: Fix MG_DP_MODE() register programming (2019-04-24 09:39:11 
> +0300)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2019-05-07
> 
> for you to fetch changes up to 75fdb811d93c8aa4a9f73b63db032b1e6a8668ef:
> 
>   drm/i915/gvt: Add in context mmio 0x20D8 to gen9 mmio list (2019-05-05 
> 17:02:25 +0800)
> 
> 
> gvt-next-fixes-2019-05-07
> 
> - Revert MCHBAR save range change for BXT regression (Yakui)
> - Align display dmabuf size for bytes instead of error-prone pages (Xiong)
> - Fix one context MMIO save/restore after RCS0 name change (Colin)
> - Misc klocwork warning/errors fixes (Aleksei)
> 
> 
> Aleksei Gimbitskii (4):
>   drm/i915/gvt: Remove typedef and let the enumeration starts from zero
>   drm/i915/gvt: Do not copy the uninitialized pointer from fb_info
>   drm/i915/gvt: Use snprintf() to prevent possible buffer overflow.
>   drm/i915/gvt: Check if get_next_pt_type() always returns a valid value
> 
> Colin Xu (1):
>   drm/i915/gvt: Add in context mmio 0x20D8 to gen9 mmio list
> 
> Xiong Zhang (1):
>   drm/i915/gvt: Change fb_info->size from pages to bytes
> 
> Zhao Yakui (1):
>   drm/i915/gvt: Revert "drm/i915/gvt: Refine the snapshort range of I915 
> MCHBAR to optimize gvt-g boot time"
> 
>  drivers/gpu/drm/i915/gvt/debugfs.c  |  4 ++--
>  drivers/gpu/drm/i915/gvt/dmabuf.c   | 19 ---
>  drivers/gpu/drm/i915/gvt/gtt.c  | 15 +--
>  drivers/gpu/drm/i915/gvt/gtt.h  | 16 
>  drivers/gpu/drm/i915/gvt/handlers.c |  4 ++--
>  drivers/gpu/drm/i915/gvt/mmio_context.c |  1 +
>  drivers/gpu/drm/i915/gvt/reg.h  |  3 ---
>  drivers/gpu/drm/i915/gvt/scheduler.c|  2 +-
>  8 files changed, 31 insertions(+), 33 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

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

[Joonas Lahtinen]

Quoting Zhenyu Wang (2019-04-16 11:48:14)
> On 2019.04.16 10:29:03 +0300, Joonas Lahtinen wrote:
> > I'm getting an error while pulling this, could you check it:
> > 
> >   From https://github.com/intel/gvt-linux
> >* tag gvt-next-2019-04-09 -> FETCH_HEAD
> >   dim: 66bd9f69d615 ("drm/i915/gvt: addressed guest GPU hang with HWS index 
> > mode"): Fixes: SHA1 in not pointing at an ancestor:
> >   dim: 54939ea0bd85 ("drm/i915: Switch to use HWS indices rather than 
> > addresses")
> >   dim: ERROR: issues in commits detected, aborting
> > 
> 
> Sorry for this, I applied gvt change earlier than back-merge one, which 
> caused this.
> Now generated new one, pls help to pull.

This is now pulled.

Regards, Joonas

> 
> Thanks.
> --
> The following changes since commit 28d618e9ab86f26a31af0b235ced55beb3e343c8:
> 
>   drm/i915: Update DRIVER_DATE to 20190404 (2019-04-04 17:43:58 +0300)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-2019-04-16
> 
> for you to fetch changes up to 2bfc4975083ace0e5777116514c3a75e59b3dbcd:
> 
>   drm/i915/gvt: Fix incorrect mask of mmio 0x22028 in gen8/9 mmio list 
> (2019-04-16 16:52:51 +0800)
> 
> 
> gvt-next-2019-04-16
> 
> - Refine range of MCHBAR snapshot (Yakui)
> - Refine out-of-sync page struct (Yakui)
> - Remove unused vGPU sreg (Yan)
> - Refind MMIO reg names (Xiaolin)
> - Proper handling of sync/async flip (Colin)
> - Proper handling of PIPE_CONTROL/MI_FLUSH_DW index mode (Xiaolin)
> - EXCC reg mask fix (Colin)
> 
> 
> Colin Xu (5):
>   drm/i915/gvt: Use consist max display pipe numbers as i915 definition
>   drm/i915/gvt: Add macro define for mmio 0x50080 and gvt flip event
>   drm/i915/gvt: Enable synchronous flip on handling MI_DISPLAY_FLIP
>   drm/i915/gvt: Enable async flip on plane surface mmio writes
>   drm/i915/gvt: Fix incorrect mask of mmio 0x22028 in gen8/9 mmio list
> 
> Xiaolin Zhang (2):
>   drm/i915/gvt: replaced register address with name
>   drm/i915/gvt: addressed guest GPU hang with HWS index mode
> 
> Yan Zhao (1):
>   drm/i915/gvt: remove the unused sreg
> 
> Zhao Yakui (2):
>   drm/i915/gvt: Refine the snapshort range of I915 MCHBAR to optimize 
> gvt-g boot time
>   drm/i915/gvt: Refine the combined intel_vgpu_oos_page struct to save 
> memory
> 
> Zhenyu Wang (1):
>   Merge tag 'drm-intel-next-2019-04-04' into gvt-next
> 
>  drivers/gpu/drm/i915/gvt/cmd_parser.c   |  30 +-
>  drivers/gpu/drm/i915/gvt/display.c  |   1 -
>  drivers/gpu/drm/i915/gvt/gtt.c  |   7 ++
>  drivers/gpu/drm/i915/gvt/gtt.h  |   2 +-
>  drivers/gpu/drm/i915/gvt/gvt.h  |   9 +-
>  drivers/gpu/drm/i915/gvt/handlers.c | 159 
> +++-
>  drivers/gpu/drm/i915/gvt/mmio.c |   8 +-
>  drivers/gpu/drm/i915/gvt/mmio_context.c |   4 +-
>  drivers/gpu/drm/i915/gvt/reg.h  |  34 +++
>  9 files changed, 172 insertions(+), 82 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

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

[Zhenyu Wang]

On 2019.04.16 10:29:03 +0300, Joonas Lahtinen wrote:
> I'm getting an error while pulling this, could you check it:
> 
>   From https://github.com/intel/gvt-linux
>* tag gvt-next-2019-04-09 -> FETCH_HEAD
>   dim: 66bd9f69d615 ("drm/i915/gvt: addressed guest GPU hang with HWS index 
> mode"): Fixes: SHA1 in not pointing at an ancestor:
>   dim: 54939ea0bd85 ("drm/i915: Switch to use HWS indices rather than 
> addresses")
>   dim: ERROR: issues in commits detected, aborting
> 

Sorry for this, I applied gvt change earlier than back-merge one, which caused 
this.
Now generated new one, pls help to pull.

Thanks.
--
The following changes since commit 28d618e9ab86f26a31af0b235ced55beb3e343c8:

  drm/i915: Update DRIVER_DATE to 20190404 (2019-04-04 17:43:58 +0300)

are available in the Git repository at:

  https://github.com/intel/gvt-linux.git tags/gvt-next-2019-04-16

for you to fetch changes up to 2bfc4975083ace0e5777116514c3a75e59b3dbcd:

  drm/i915/gvt: Fix incorrect mask of mmio 0x22028 in gen8/9 mmio list 
(2019-04-16 16:52:51 +0800)


gvt-next-2019-04-16

- Refine range of MCHBAR snapshot (Yakui)
- Refine out-of-sync page struct (Yakui)
- Remove unused vGPU sreg (Yan)
- Refind MMIO reg names (Xiaolin)
- Proper handling of sync/async flip (Colin)
- Proper handling of PIPE_CONTROL/MI_FLUSH_DW index mode (Xiaolin)
- EXCC reg mask fix (Colin)


Colin Xu (5):
  drm/i915/gvt: Use consist max display pipe numbers as i915 definition
  drm/i915/gvt: Add macro define for mmio 0x50080 and gvt flip event
  drm/i915/gvt: Enable synchronous flip on handling MI_DISPLAY_FLIP
  drm/i915/gvt: Enable async flip on plane surface mmio writes
  drm/i915/gvt: Fix incorrect mask of mmio 0x22028 in gen8/9 mmio list

Xiaolin Zhang (2):
  drm/i915/gvt: replaced register address with name
  drm/i915/gvt: addressed guest GPU hang with HWS index mode

Yan Zhao (1):
  drm/i915/gvt: remove the unused sreg

Zhao Yakui (2):
  drm/i915/gvt: Refine the snapshort range of I915 MCHBAR to optimize gvt-g 
boot time
  drm/i915/gvt: Refine the combined intel_vgpu_oos_page struct to save 
memory

Zhenyu Wang (1):
  Merge tag 'drm-intel-next-2019-04-04' into gvt-next

 drivers/gpu/drm/i915/gvt/cmd_parser.c   |  30 +-
 drivers/gpu/drm/i915/gvt/display.c  |   1 -
 drivers/gpu/drm/i915/gvt/gtt.c  |   7 ++
 drivers/gpu/drm/i915/gvt/gtt.h  |   2 +-
 drivers/gpu/drm/i915/gvt/gvt.h  |   9 +-
 drivers/gpu/drm/i915/gvt/handlers.c | 159 +++-
 drivers/gpu/drm/i915/gvt/mmio.c |   8 +-
 drivers/gpu/drm/i915/gvt/mmio_context.c |   4 +-
 drivers/gpu/drm/i915/gvt/reg.h  |  34 +++
 9 files changed, 172 insertions(+), 82 deletions(-)


-- 
Open Source Technology Center, Intel ltd.

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


signature.asc
Description: PGP signature
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Joonas Lahtinen]

I'm getting an error while pulling this, could you check it:

  From https://github.com/intel/gvt-linux
   * tag gvt-next-2019-04-09 -> FETCH_HEAD
  dim: 66bd9f69d615 ("drm/i915/gvt: addressed guest GPU hang with HWS index 
mode"): Fixes: SHA1 in not pointing at an ancestor:
  dim: 54939ea0bd85 ("drm/i915: Switch to use HWS indices rather than 
addresses")
  dim: ERROR: issues in commits detected, aborting

Best Regards,
Joonas

Quoting Zhenyu Wang (2019-04-09 07:05:00)
> 
> Hi,
> 
> This includes various code refinement and cleanups, with proper
> async/sync display flip handling, and also some changes required
> for recent drm-intel-next as guest kernel, details below.
> 
> Thanks
> --
> The following changes since commit a01b2c6f47d86c7d1a9fa822b3b91ec233b61784:
> 
>   drm/i915: Update DRIVER_DATE to 20190328 (2019-03-28 14:41:55 +0200)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-2019-04-09
> 
> for you to fetch changes up to 201e3e8580bb4924d0cc29fc3841ea5782401b46:
> 
>   drm/i915/gvt: Fix incorrect mask of mmio 0x22028 in gen8/9 mmio list 
> (2019-04-03 16:37:20 +0800)
> 
> 
> gvt-next-2019-04-09
> 
> - Refine range of MCHBAR snapshot (Yakui)
> - Refine out-of-sync page struct (Yakui)
> - Remove unused vGPU sreg (Yan)
> - Refind MMIO reg names (Xiaolin)
> - Proper handling of sync/async flip (Colin)
> - Proper handling of PIPE_CONTROL/MI_FLUSH_DW index mode (Xiaolin)
> - EXCC reg mask fix (Colin)
> 
> 
> Colin Xu (5):
>   drm/i915/gvt: Use consist max display pipe numbers as i915 definition
>   drm/i915/gvt: Add macro define for mmio 0x50080 and gvt flip event
>   drm/i915/gvt: Enable synchronous flip on handling MI_DISPLAY_FLIP
>   drm/i915/gvt: Enable async flip on plane surface mmio writes
>   drm/i915/gvt: Fix incorrect mask of mmio 0x22028 in gen8/9 mmio list
> 
> Xiaolin Zhang (2):
>   drm/i915/gvt: replaced register address with name
>   drm/i915/gvt: addressed guest GPU hang with HWS index mode
> 
> Yan Zhao (1):
>   drm/i915/gvt: remove the unused sreg
> 
> Zhao Yakui (2):
>   drm/i915/gvt: Refine the snapshort range of I915 MCHBAR to optimize 
> gvt-g boot time
>   drm/i915/gvt: Refine the combined intel_vgpu_oos_page struct to save 
> memory
> 
> Zhenyu Wang (1):
>   Merge tag 'drm-intel-next-2019-03-28' into gvt-next
> 
>  drivers/gpu/drm/i915/gvt/cmd_parser.c   |  30 +-
>  drivers/gpu/drm/i915/gvt/display.c  |   1 -
>  drivers/gpu/drm/i915/gvt/gtt.c  |   7 ++
>  drivers/gpu/drm/i915/gvt/gtt.h  |   2 +-
>  drivers/gpu/drm/i915/gvt/gvt.h  |   9 +-
>  drivers/gpu/drm/i915/gvt/handlers.c | 159 
> +++-
>  drivers/gpu/drm/i915/gvt/mmio.c |   8 +-
>  drivers/gpu/drm/i915/gvt/mmio_context.c |   4 +-
>  drivers/gpu/drm/i915/gvt/reg.h  |  34 +++
>  9 files changed, 172 insertions(+), 82 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

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

[Rodrigo Vivi]

On Fri, Feb 01, 2019 at 02:15:23PM +0800, Zhenyu Wang wrote:
> 
> Hi,
> 
> This should be last gvt-next pull for this round, which adds VFIO edid
> region support in GVT, VM manager can use this to specify custom EDID
> for VM, which can be used for e.g UI resize, etc.

Pulled, thanks

> 
> p.s, Next week will be chinese new year, so team will be offline then.

Happy New Year!

> 
> Thanks.
> --
> The following changes since commit 2e679d48f38c378650db403b4ba2248adf0691b2:
> 
>   drm/i915/gvt: switch to kernel types (2019-01-23 13:56:14 +0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-2019-02-01
> 
> for you to fetch changes up to 39c68e87bc50a71bcfe93582d9b0673ef30db418:
> 
>   drm/i915/gvt: add VFIO EDID region (2019-01-31 11:41:25 +0800)
> 
> 
> gvt-next-2019-02-01
> 
> - new VFIO EDID region support (Henry)
> 
> 
> Hang Yuan (3):
>   drm/i915/gvt: add functions to get default resolution
>   drm/i915/gvt: add hotplug emulation
>   drm/i915/gvt: add VFIO EDID region
> 
>  drivers/gpu/drm/i915/gvt/display.c   |  31 
>  drivers/gpu/drm/i915/gvt/display.h   |  37 +++--
>  drivers/gpu/drm/i915/gvt/gvt.c   |   1 +
>  drivers/gpu/drm/i915/gvt/gvt.h   |   3 +
>  drivers/gpu/drm/i915/gvt/hypercall.h |   1 +
>  drivers/gpu/drm/i915/gvt/kvmgt.c | 143 
> +++
>  drivers/gpu/drm/i915/gvt/mpt.h   |  17 +
>  drivers/gpu/drm/i915/gvt/vgpu.c  |   6 ++
>  8 files changed, 233 insertions(+), 6 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 mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Rodrigo Vivi]

On Thu, Jan 24, 2019 at 01:40:48PM +0800, Zhenyu Wang wrote:
> 
> Hi,
> 
> Here is gvt-next stuff. This includes Coffeelake support for GVT,
> making kvmgt as self load module to have better dependence with
> vfio/mdev, with some const treatment and kernel type change.

ops, I also failed to let you know I had pulled this.

I also already sent in previous pull request to Dave and Daniel.

Sorry,
Rodrigo.

> 
> Thanks.
> --
> The following changes since commit d1810909d841314ba94b14dc3de9e9fbc13b046a:
> 
>   drm/i915/gvt: fix spelling mistake "Interupts" -> "Interrupts" (2018-12-07 
> 12:01:09 +0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-2019-01-24
> 
> for you to fetch changes up to 2e679d48f38c378650db403b4ba2248adf0691b2:
> 
>   drm/i915/gvt: switch to kernel types (2019-01-23 13:56:14 +0800)
> 
> 
> gvt-next-2019-01-24
> 
> - split kvmgt as seperate module (Zhenyu)
> - Coffeelake GVT support (Fred)
> - const treatment and change for kernel type (Jani)
> 
> 
> Jani Nikula (4):
>   drm/i915/gvt: remove drmP.h include
>   drm/i915/gvt: give the cmd parser decode_info a const treatment
>   drm/i915/gvt: give the cmd parser cmd_info a const treatment
>   drm/i915/gvt: switch to kernel types
> 
> Zhenyu Wang (3):
>   drm/i915/gvt: mandatory require hypervisor's host_init
>   drm/i915/gvt: remove unused parameter for hypervisor's host_exit call
>   drm/i915/gvt: Change KVMGT as self load module
> 
> fred gao (6):
>   drm/i915/gvt: Add coffeelake platform definition
>   drm/i915/gvt: Add mmio handler for CFL
>   drm/i915/gvt: Enable gfx virtualiztion for CFL
>   drm/i915/gvt: Reuse the gmbus pin macro
>   drm/i915/gvt: Refine port select logic for CFL platform
>   drm/i915: Enable gfx virtualization for Coffeelake platform
> 
>  drivers/gpu/drm/i915/Makefile   |   1 +
>  drivers/gpu/drm/i915/gvt/Makefile   |   1 -
>  drivers/gpu/drm/i915/gvt/cmd_parser.c   |  83 
>  drivers/gpu/drm/i915/gvt/display.c  |  12 ++--
>  drivers/gpu/drm/i915/gvt/dmabuf.c   |   5 +-
>  drivers/gpu/drm/i915/gvt/edid.c |  32 +++---
>  drivers/gpu/drm/i915/gvt/fb_decoder.c   |  12 +---
>  drivers/gpu/drm/i915/gvt/gvt.c  | 108 
> +---
>  drivers/gpu/drm/i915/gvt/gvt.h  |   6 +-
>  drivers/gpu/drm/i915/gvt/handlers.c |  29 -
>  drivers/gpu/drm/i915/gvt/hypercall.h|   9 ++-
>  drivers/gpu/drm/i915/gvt/interrupt.c|   4 +-
>  drivers/gpu/drm/i915/gvt/kvmgt.c|  42 -
>  drivers/gpu/drm/i915/gvt/mmio.c |   6 +-
>  drivers/gpu/drm/i915/gvt/mmio.h |  11 ++--
>  drivers/gpu/drm/i915/gvt/mmio_context.c |  18 +++---
>  drivers/gpu/drm/i915/gvt/mpt.h  |  13 ++--
>  drivers/gpu/drm/i915/gvt/sched_policy.c |   2 +-
>  drivers/gpu/drm/i915/gvt/scheduler.c|   7 +--
>  drivers/gpu/drm/i915/gvt/scheduler.h|   2 +-
>  drivers/gpu/drm/i915/gvt/trace.h|   2 +-
>  drivers/gpu/drm/i915/intel_gvt.c|  12 +---
>  22 files changed, 204 insertions(+), 213 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 mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] [PULL] gvt-next for 4.21

[Jani Nikula]

On Tue, 11 Dec 2018, Zhenyu Wang  wrote:
> On 2018.12.10 16:41:24 -0800, Rodrigo Vivi wrote:
>> 
>> On Fri, Dec 07, 2018 at 12:36:59PM +0800, Zhenyu Wang wrote:
>> > 
>> > Hi,
>> > 
>> > As I was hoping to possibly merge more new stuff for next kernel e.g
>> > CFL support, etc, but seems those're still not stable enough so better
>> > wait for next cycle, so sorry for the late.
>> 
>> If I understood correctly Jani already sent the latest pull request
>> targeting 4.21. Right Jani?
>>
>> Should we start queueing this for 4.22?
>>
>
> yeah, sorry I missed that window, but this one actually contains stuff
> for -next-fixes besides typo fixes, otherwise 4.21 will be problematic.
> Let me generate another one for dinf.

I've pulled this to drm-intel-next-fixes, headed to v4.21.

Thanks,
Jani.


>
> thanks
>
>> > 
>> > This includes mostly one regression fix for drm-intel-next when we
>> > introduced during previous shadow ctx ppgtt failure fix patch, and one
>> > update on force-to-nonpriv register list. There're also three typo
>> > fixes we received, I think they're trivial so should be no harm to
>> > include.
>> > 
>> > Thanks
>> > --
>> > The following changes since commit 
>> > 4377d4e0d3d511986033ba7b4182d5a80b7f9ea2:
>> > 
>> >   drm/i915: Update DRIVER_DATE to 20181204 (2018-12-04 19:26:17 +0200)
>> > 
>> > are available in the Git repository at:
>> > 
>> >   https://github.com/intel/gvt-linux.git tags/gvt-next-2018-12-07
>> > 
>> > for you to fetch changes up to d1810909d841314ba94b14dc3de9e9fbc13b046a:
>> > 
>> >   drm/i915/gvt: fix spelling mistake "Interupts" -> "Interrupts" 
>> > (2018-12-07 12:01:09 +0800)
>> > 
>> > 
>> > gvt-next-2018-12-07
>> > 
>> > - Fix -next regression on shadow ctx's ppgtt destroy (Xiong)
>> > - Update force-to-nonpriv register list (Yan)
>> > - three typo fixes
>> > 
>> > 
>> > Colin Ian King (1):
>> >   drm/i915/gvt: fix spelling mistake "Interupts" -> "Interrupts"
>> > 
>> > Peng Hao (1):
>> >   drm/i915/gvt: fix a typo: "registeration" -> "registration".
>> > 
>> > Xinyun Liu (1):
>> >   drm/i915/gvt: fix typo in two MI cmd annotation
>> > 
>> > Xiong Zhang (1):
>> >   drm/i915/gvt: Fix shadow ctx ppgtt destroy function
>> > 
>> > Zhao Yan (1):
>> >   drm/i915/gvt: update force-to-nonpriv register whitelist
>> > 
>> >  drivers/gpu/drm/i915/gvt/cmd_parser.c |  6 +++---
>> >  drivers/gpu/drm/i915/gvt/gvt.c|  2 +-
>> >  drivers/gpu/drm/i915/gvt/gvt.h|  4 
>> >  drivers/gpu/drm/i915/gvt/handlers.c   |  1 +
>> >  drivers/gpu/drm/i915/gvt/interrupt.c  |  2 +-
>> >  drivers/gpu/drm/i915/gvt/scheduler.c  | 33 
>> > +
>> >  6 files changed, 43 insertions(+), 5 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
>> 

-- 
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 for 4.21

[Zhenyu Wang]

On 2018.12.10 16:41:24 -0800, Rodrigo Vivi wrote:
> 
> On Fri, Dec 07, 2018 at 12:36:59PM +0800, Zhenyu Wang wrote:
> > 
> > Hi,
> > 
> > As I was hoping to possibly merge more new stuff for next kernel e.g
> > CFL support, etc, but seems those're still not stable enough so better
> > wait for next cycle, so sorry for the late.
> 
> If I understood correctly Jani already sent the latest pull request
> targeting 4.21. Right Jani?
>
> Should we start queueing this for 4.22?
>

yeah, sorry I missed that window, but this one actually contains stuff
for -next-fixes besides typo fixes, otherwise 4.21 will be problematic.
Let me generate another one for dinf.

thanks

> > 
> > This includes mostly one regression fix for drm-intel-next when we
> > introduced during previous shadow ctx ppgtt failure fix patch, and one
> > update on force-to-nonpriv register list. There're also three typo
> > fixes we received, I think they're trivial so should be no harm to
> > include.
> > 
> > Thanks
> > --
> > The following changes since commit 4377d4e0d3d511986033ba7b4182d5a80b7f9ea2:
> > 
> >   drm/i915: Update DRIVER_DATE to 20181204 (2018-12-04 19:26:17 +0200)
> > 
> > are available in the Git repository at:
> > 
> >   https://github.com/intel/gvt-linux.git tags/gvt-next-2018-12-07
> > 
> > for you to fetch changes up to d1810909d841314ba94b14dc3de9e9fbc13b046a:
> > 
> >   drm/i915/gvt: fix spelling mistake "Interupts" -> "Interrupts" 
> > (2018-12-07 12:01:09 +0800)
> > 
> > 
> > gvt-next-2018-12-07
> > 
> > - Fix -next regression on shadow ctx's ppgtt destroy (Xiong)
> > - Update force-to-nonpriv register list (Yan)
> > - three typo fixes
> > 
> > 
> > Colin Ian King (1):
> >   drm/i915/gvt: fix spelling mistake "Interupts" -> "Interrupts"
> > 
> > Peng Hao (1):
> >   drm/i915/gvt: fix a typo: "registeration" -> "registration".
> > 
> > Xinyun Liu (1):
> >   drm/i915/gvt: fix typo in two MI cmd annotation
> > 
> > Xiong Zhang (1):
> >   drm/i915/gvt: Fix shadow ctx ppgtt destroy function
> > 
> > Zhao Yan (1):
> >   drm/i915/gvt: update force-to-nonpriv register whitelist
> > 
> >  drivers/gpu/drm/i915/gvt/cmd_parser.c |  6 +++---
> >  drivers/gpu/drm/i915/gvt/gvt.c|  2 +-
> >  drivers/gpu/drm/i915/gvt/gvt.h|  4 
> >  drivers/gpu/drm/i915/gvt/handlers.c   |  1 +
> >  drivers/gpu/drm/i915/gvt/interrupt.c  |  2 +-
> >  drivers/gpu/drm/i915/gvt/scheduler.c  | 33 
> > +
> >  6 files changed, 43 insertions(+), 5 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
> 

-- 
Open Source Technology Center, Intel ltd.

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


signature.asc
Description: PGP signature
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] [PULL] gvt-next for 4.21

[Rodrigo Vivi]

On Fri, Dec 07, 2018 at 12:36:59PM +0800, Zhenyu Wang wrote:
> 
> Hi,
> 
> As I was hoping to possibly merge more new stuff for next kernel e.g
> CFL support, etc, but seems those're still not stable enough so better
> wait for next cycle, so sorry for the late.

If I understood correctly Jani already sent the latest pull request
targeting 4.21. Right Jani?

Should we start queueing this for 4.22?

> 
> This includes mostly one regression fix for drm-intel-next when we
> introduced during previous shadow ctx ppgtt failure fix patch, and one
> update on force-to-nonpriv register list. There're also three typo
> fixes we received, I think they're trivial so should be no harm to
> include.
> 
> Thanks
> --
> The following changes since commit 4377d4e0d3d511986033ba7b4182d5a80b7f9ea2:
> 
>   drm/i915: Update DRIVER_DATE to 20181204 (2018-12-04 19:26:17 +0200)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-2018-12-07
> 
> for you to fetch changes up to d1810909d841314ba94b14dc3de9e9fbc13b046a:
> 
>   drm/i915/gvt: fix spelling mistake "Interupts" -> "Interrupts" (2018-12-07 
> 12:01:09 +0800)
> 
> 
> gvt-next-2018-12-07
> 
> - Fix -next regression on shadow ctx's ppgtt destroy (Xiong)
> - Update force-to-nonpriv register list (Yan)
> - three typo fixes
> 
> 
> Colin Ian King (1):
>   drm/i915/gvt: fix spelling mistake "Interupts" -> "Interrupts"
> 
> Peng Hao (1):
>   drm/i915/gvt: fix a typo: "registeration" -> "registration".
> 
> Xinyun Liu (1):
>   drm/i915/gvt: fix typo in two MI cmd annotation
> 
> Xiong Zhang (1):
>   drm/i915/gvt: Fix shadow ctx ppgtt destroy function
> 
> Zhao Yan (1):
>   drm/i915/gvt: update force-to-nonpriv register whitelist
> 
>  drivers/gpu/drm/i915/gvt/cmd_parser.c |  6 +++---
>  drivers/gpu/drm/i915/gvt/gvt.c|  2 +-
>  drivers/gpu/drm/i915/gvt/gvt.h|  4 
>  drivers/gpu/drm/i915/gvt/handlers.c   |  1 +
>  drivers/gpu/drm/i915/gvt/interrupt.c  |  2 +-
>  drivers/gpu/drm/i915/gvt/scheduler.c  | 33 +
>  6 files changed, 43 insertions(+), 5 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 mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Joonas Lahtinen]

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
> > > with proper invalidate of old entry. Another one for one
> > > chicken reg mask fix.
> > > 
> > > thanks
> > 
> > Hi,
> > 
> > DIM seems to be (rightfully) complaining about one commit:
> > 
> > 3e740f0ec37acecaa364c19d2d2826df83c8bf20 is lacking committer of sign-off
> > 
> > Probably better if you re-submit the PR for -fixes (rebased for
> > v4.20-rc1).
> > 
> 
> Looks -fixes is still 4.19? So I still regenerate against -next-fixes,
> let me know if that's ok for you.

Ok, I've now pushed first set of -fixes aiming at v4.20-rc2 to
drm-intel-fixes. Now is good time to respin.

Regards, Joonas

> 
> Thanks
> --
> 
> The following changes since commit 835fe6d75d14c1513910ed7f5665127fee12acc8:
> 
>   firmware/dmc/icl: Add missing MODULE_FIRMWARE() for Icelake. (2018-10-18 
> 10:36:10 +0300)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2018-10-26
> 
> for you to fetch changes up to 348589205265049eda2e365371eec18d56809699:
> 
>   drm/i915/gvt: correct mask setting for CSFE_CHICKEN1 (2018-10-26 10:57:48 
> +0800)
> 
> 
> gvt-next-fixes-2018-10-26
> 
> - Fix invalidate of old ggtt entry (Hang)
> - Fix partial ggtt entry update in any order (Hang)
> - Fix one mask setting for chicken reg (Xinyun)
> 
> 
> Hang Yuan (2):
>   drm/i915/gvt: invalidate old ggtt page when update ggtt entry
>   drm/i915/gvt: support inconsecutive partial gtt entry write
> 
> Xinyun Liu (1):
>   drm/i915/gvt: correct mask setting for CSFE_CHICKEN1
> 
>  drivers/gpu/drm/i915/gvt/gtt.c  | 115 
> 
>  drivers/gpu/drm/i915/gvt/gtt.h  |   9 ++-
>  drivers/gpu/drm/i915/gvt/mmio_context.c |   2 +-
>  3 files changed, 66 insertions(+), 60 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

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

[Zhenyu Wang]

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
> > chicken reg mask fix.
> > 
> > thanks
> 
> Hi,
> 
> DIM seems to be (rightfully) complaining about one commit:
> 
> 3e740f0ec37acecaa364c19d2d2826df83c8bf20 is lacking committer of sign-off
> 
> Probably better if you re-submit the PR for -fixes (rebased for
> v4.20-rc1).
> 

Looks -fixes is still 4.19? So I still regenerate against -next-fixes,
let me know if that's ok for you.

Thanks
--

The following changes since commit 835fe6d75d14c1513910ed7f5665127fee12acc8:

  firmware/dmc/icl: Add missing MODULE_FIRMWARE() for Icelake. (2018-10-18 
10:36:10 +0300)

are available in the Git repository at:

  https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2018-10-26

for you to fetch changes up to 348589205265049eda2e365371eec18d56809699:

  drm/i915/gvt: correct mask setting for CSFE_CHICKEN1 (2018-10-26 10:57:48 
+0800)


gvt-next-fixes-2018-10-26

- Fix invalidate of old ggtt entry (Hang)
- Fix partial ggtt entry update in any order (Hang)
- Fix one mask setting for chicken reg (Xinyun)


Hang Yuan (2):
  drm/i915/gvt: invalidate old ggtt page when update ggtt entry
  drm/i915/gvt: support inconsecutive partial gtt entry write

Xinyun Liu (1):
  drm/i915/gvt: correct mask setting for CSFE_CHICKEN1

 drivers/gpu/drm/i915/gvt/gtt.c  | 115 
 drivers/gpu/drm/i915/gvt/gtt.h  |   9 ++-
 drivers/gpu/drm/i915/gvt/mmio_context.c |   2 +-
 3 files changed, 66 insertions(+), 60 deletions(-)


-- 
Open Source Technology Center, Intel ltd.

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


signature.asc
Description: PGP signature
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Zhenyu Wang]

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 GGTT entry and
> > > with proper invalidate of old entry. Another one for one
> > > chicken reg mask fix.
> > > 
> > > thanks
> > 
> > Hi,
> > 
> > DIM seems to be (rightfully) complaining about one commit:
> > 
> > 3e740f0ec37acecaa364c19d2d2826df83c8bf20 is lacking committer of sign-off
> 
> This is something I'm asking gvt for a while already:
> Please make review mandatory on your side.
>

yes, we are appling review process more strictly on gvt side,
that one should be reviewed by Zhi when I was offline, but he
seems forget to add r-b and I forgot to sign-off...Sorry for that,
will regenerate.

-- 
Open Source Technology Center, Intel ltd.

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


signature.asc
Description: PGP signature
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Rodrigo Vivi]

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 one for one
> > chicken reg mask fix.
> > 
> > thanks
> 
> Hi,
> 
> DIM seems to be (rightfully) complaining about one commit:
> 
> 3e740f0ec37acecaa364c19d2d2826df83c8bf20 is lacking committer of sign-off

This is something I'm asking gvt for a while already:
Please make review mandatory on your side.

> 
> Probably better if you re-submit the PR for -fixes (rebased for
> v4.20-rc1).
> 
> Regards, Joonas
> 
> > --
> > The following changes since commit 835fe6d75d14c1513910ed7f5665127fee12acc8:
> > 
> >   firmware/dmc/icl: Add missing MODULE_FIRMWARE() for Icelake. (2018-10-18 
> > 10:36:10 +0300)
> > 
> > are available in the Git repository at:
> > 
> >   https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2018-10-23
> > 
> > for you to fetch changes up to 3e740f0ec37acecaa364c19d2d2826df83c8bf20:
> > 
> >   drm/i915/gvt: correct mask setting for CSFE_CHICKEN1 (2018-10-19 11:32:41 
> > +0800)
> > 
> > 
> > gvt-next-fixes-2018-10-23
> > 
> > - Fix invalidate of old ggtt entry (Hang)
> > - Fix partial ggtt entry update in any order (Hang)
> > - Fix one mask setting for chicken reg (Xinyun)
> > 
> > 
> > Hang Yuan (2):
> >   drm/i915/gvt: invalidate old ggtt page when update ggtt entry
> >   drm/i915/gvt: support inconsecutive partial gtt entry write
> > 
> > Xinyun Liu (1):
> >   drm/i915/gvt: correct mask setting for CSFE_CHICKEN1
> > 
> >  drivers/gpu/drm/i915/gvt/gtt.c  | 115 
> > 
> >  drivers/gpu/drm/i915/gvt/gtt.h  |   9 ++-
> >  drivers/gpu/drm/i915/gvt/mmio_context.c |   2 +-
> >  3 files changed, 66 insertions(+), 60 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 mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Joonas Lahtinen]

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 (rightfully) complaining about one commit:

3e740f0ec37acecaa364c19d2d2826df83c8bf20 is lacking committer of sign-off

Probably better if you re-submit the PR for -fixes (rebased for
v4.20-rc1).

Regards, Joonas

> --
> The following changes since commit 835fe6d75d14c1513910ed7f5665127fee12acc8:
> 
>   firmware/dmc/icl: Add missing MODULE_FIRMWARE() for Icelake. (2018-10-18 
> 10:36:10 +0300)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2018-10-23
> 
> for you to fetch changes up to 3e740f0ec37acecaa364c19d2d2826df83c8bf20:
> 
>   drm/i915/gvt: correct mask setting for CSFE_CHICKEN1 (2018-10-19 11:32:41 
> +0800)
> 
> 
> gvt-next-fixes-2018-10-23
> 
> - Fix invalidate of old ggtt entry (Hang)
> - Fix partial ggtt entry update in any order (Hang)
> - Fix one mask setting for chicken reg (Xinyun)
> 
> 
> Hang Yuan (2):
>   drm/i915/gvt: invalidate old ggtt page when update ggtt entry
>   drm/i915/gvt: support inconsecutive partial gtt entry write
> 
> Xinyun Liu (1):
>   drm/i915/gvt: correct mask setting for CSFE_CHICKEN1
> 
>  drivers/gpu/drm/i915/gvt/gtt.c  | 115 
> 
>  drivers/gpu/drm/i915/gvt/gtt.h  |   9 ++-
>  drivers/gpu/drm/i915/gvt/mmio_context.c |   2 +-
>  3 files changed, 66 insertions(+), 60 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

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

[Zhenyu Wang]

On 2018.09.06 16:11:20 +0300, Joonas Lahtinen wrote:
> Quoting Zhenyu Wang (2018-09-04 06:01:54)
> > 
> > Hi,
> > 
> > Here's initial gvt-next for 4.20 with two optimization for
> > guest context shadowing and command parser, and with W=1 build fixes.
> 
> Thanks, pulled this, but it had one merge conflict (in gvt/reg.h).
> Please make sure the resolution I put in into drm-intel-next is correct.
> 

yeah, forgot to mention conflict with recent PCH reg define
change. Merge change is correct.

Thanks!

-- 
Open Source Technology Center, Intel ltd.

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


signature.asc
Description: PGP signature
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Joonas Lahtinen]

Quoting Zhenyu Wang (2018-09-04 06:01:54)
> 
> Hi,
> 
> Here's initial gvt-next for 4.20 with two optimization for
> guest context shadowing and command parser, and with W=1 build fixes.

Thanks, pulled this, but it had one merge conflict (in gvt/reg.h).
Please make sure the resolution I put in into drm-intel-next is correct.

Regards, Joonas

> 
> Thanks
> --
> The following changes since commit 279ce5d117078ee8ea40c40199399889981fd808:
> 
>   drm/i915/gvt: declare gvt as i915's soft dependency (2018-07-10 11:13:11 
> +0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-2018-09-04
> 
> for you to fetch changes up to 69ca5af4ff9a3ff96e4595c2b7522c01a2641779:
> 
>   drm/i915/gvt: Move some MMIO definitions to reg.h (2018-08-07 10:40:11 
> +0800)
> 
> 
> gvt-next-2018-09-04
> 
> - guest context shadow optimization for restore inhibit one (Yan)
> - cmd parser optimization (Yan)
> - W=1 warning fixes (Zhenyu)
> 
> 
> Zhao Yan (2):
>   drm/i915/gvt: add a fastpath for cmd parsing on MI_NOOP
>   drm/i915/gvt: only copy the first page for restore inhibit context
> 
> Zhenyu Wang (3):
>   drm/i915/gvt: make dma map/unmap kvmgt functions as static
>   drm/i915/gvt: Fix function comment doc errors
>   drm/i915/gvt: Move some MMIO definitions to reg.h
> 
>  drivers/gpu/drm/i915/gvt/cfg_space.c| 12 +++
>  drivers/gpu/drm/i915/gvt/cmd_parser.c   | 11 +-
>  drivers/gpu/drm/i915/gvt/display.c  |  1 +
>  drivers/gpu/drm/i915/gvt/edid.c |  9 +
>  drivers/gpu/drm/i915/gvt/gtt.c  |  9 +++--
>  drivers/gpu/drm/i915/gvt/gvt.c  |  3 +-
>  drivers/gpu/drm/i915/gvt/handlers.c |  1 +
>  drivers/gpu/drm/i915/gvt/kvmgt.c|  4 +--
>  drivers/gpu/drm/i915/gvt/mmio.c |  3 +-
>  drivers/gpu/drm/i915/gvt/mmio_context.c | 13 ---
>  drivers/gpu/drm/i915/gvt/mmio_context.h |  3 ++
>  drivers/gpu/drm/i915/gvt/opregion.c |  1 -
>  drivers/gpu/drm/i915/gvt/page_track.c   |  2 ++
>  drivers/gpu/drm/i915/gvt/reg.h  |  9 +
>  drivers/gpu/drm/i915/gvt/scheduler.c| 64 
> +
>  15 files changed, 92 insertions(+), 53 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

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

[Rodrigo Vivi]

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:
> 
>   drm/i915/kvmgt: Fix compilation error (2018-08-06 11:28:35 -0700)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2018-08-14
> 
> for you to fetch changes up to 7590ebb8b456464e48840a6d106a0c07de6d723a:
> 
>   drm/i915/gvt: fix memory leak in intel_vgpu_ioctl() (2018-08-14 15:27:12 
> +0800)
> 
> 
> gvt-next-fixes-2018-08-14
> 
> - Fix an error code in gvt_dma_map_page() (Dan)
> - Fix off by one error in intel_vgpu_write_fence() (Dan)
> - Fix potential Spectre v1 (Gustavo)
> - Fix workload free in vgpu release (Henry)
> - Fix cleanup sequence in intel_gvt_clean_device (Henry)
> - dmabuf mutex init place fix (Henry)
> - possible memory leak in intel_vgpu_ioctl() err path (Yi)
> - return error on cmd access check failure (Yan)
> 
> 
> Dan Carpenter (2):
>   drm/i915/kvmgt: fix an error code in gvt_dma_map_page()
>   drm/i915/gvt: Off by one in intel_vgpu_write_fence()
> 
> Gustavo A. R. Silva (1):
>   drm/i915/kvmgt: Fix potential Spectre v1
> 
> Hang Yuan (3):
>   drm/i915/gvt: free workload in vgpu release
>   drm/i915/gvt: fix cleanup sequence in intel_gvt_clean_device
>   drm/i915/gvt: initialize dmabuf mutex in vgpu_create
> 
> Yi Wang (1):
>   drm/i915/gvt: fix memory leak in intel_vgpu_ioctl()
> 
> Zhao Yan (1):
>   drm/i915/gvt: return error on cmd access
> 
>  drivers/gpu/drm/i915/gvt/aperture_gm.c |  2 +-
>  drivers/gpu/drm/i915/gvt/cmd_parser.c  |  2 +-
>  drivers/gpu/drm/i915/gvt/gvt.c | 15 +++
>  drivers/gpu/drm/i915/gvt/gvt.h |  4 +++-
>  drivers/gpu/drm/i915/gvt/kvmgt.c   | 26 ++
>  drivers/gpu/drm/i915/gvt/scheduler.c   |  7 ---
>  drivers/gpu/drm/i915/gvt/scheduler.h   |  3 +++
>  drivers/gpu/drm/i915/gvt/vgpu.c| 23 +--
>  8 files changed, 58 insertions(+), 24 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

Re: [Intel-gfx] [PULL] gvt-next for 4.19

[Zhenyu Wang]

On 2018.07.16 23:07:35 -0700, Rodrigo Vivi wrote:
> On Tue, Jul 17, 2018 at 12:58:37PM +0800, Zhenyu Wang wrote:
> > 
> > Hi,
> > 
> > Left fixes for all W=1 warnings, I think better to send
> > to catch up last train for 4.19, mostly kernel doc comments
> > fixes with a trivial refactor.
> 
> I was going to pull it and by pass dim...
> 
> The changes on the patches themselves is something simple enough that I would
> ack myself, although in one of patches if we had review I'm sure
> that would become 2 patches
> 
> So at this point I'm not sure if I should bypass dim or request
> another eyes... so I'm just, at least, holding until tomorrow...
> 

Sorry for bothering you, let me rework this and ask proper review for next try.
You can ignore this one.

thanks

> > --
> > The following changes since commit 279ce5d117078ee8ea40c40199399889981fd808:
> > 
> >   drm/i915/gvt: declare gvt as i915's soft dependency (2018-07-10 11:13:11 
> > +0800)
> > 
> > are available in the Git repository at:
> > 
> >   https://github.com/intel/gvt-linux.git tags/gvt-next-2018-07-17
> > 
> > for you to fetch changes up to 3e494c2eb417715cdfed66827a5752e41de748c3:
> > 
> >   drm/i915/gvt: Fix W=1 warnings (2018-07-16 13:28:47 +0800)
> > 
> > 
> > gvt-next-2018-07-17
> > 
> > - Fix all left W=1 warnings
> > 
> > 
> > Zhenyu Wang (2):
> >   drm/i915/gvt: make dma map/unmap kvmgt functions as static
> >   drm/i915/gvt: Fix W=1 warnings
> > 
> >  drivers/gpu/drm/i915/gvt/cfg_space.c| 12 
> >  drivers/gpu/drm/i915/gvt/display.c  |  1 +
> >  drivers/gpu/drm/i915/gvt/edid.c |  9 +
> >  drivers/gpu/drm/i915/gvt/gtt.c  |  9 ++---
> >  drivers/gpu/drm/i915/gvt/gvt.c  |  3 +--
> >  drivers/gpu/drm/i915/gvt/handlers.c |  1 +
> >  drivers/gpu/drm/i915/gvt/kvmgt.c|  4 ++--
> >  drivers/gpu/drm/i915/gvt/mmio.c |  3 ++-
> >  drivers/gpu/drm/i915/gvt/mmio_context.c | 13 -
> >  drivers/gpu/drm/i915/gvt/opregion.c |  1 -
> >  drivers/gpu/drm/i915/gvt/page_track.c   |  2 ++
> >  drivers/gpu/drm/i915/gvt/reg.h  |  9 +
> >  drivers/gpu/drm/i915/gvt/scheduler.c|  4 +++-
> >  13 files changed, 48 insertions(+), 23 deletions(-)
> > 
> > 
> > -- 
> > Open Source Technology Center, Intel ltd.
> > 
> > $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
> 
> 
> ___
> intel-gvt-dev mailing list
> intel-gvt-...@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


signature.asc
Description: PGP signature
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] [PULL] gvt-next for 4.19

[Rodrigo Vivi]

On Tue, Jul 17, 2018 at 12:58:37PM +0800, Zhenyu Wang wrote:
> 
> Hi,
> 
> Left fixes for all W=1 warnings, I think better to send
> to catch up last train for 4.19, mostly kernel doc comments
> fixes with a trivial refactor.

I was going to pull it and by pass dim...

The changes on the patches themselves is something simple enough that I would
ack myself, although in one of patches if we had review I'm sure
that would become 2 patches

So at this point I'm not sure if I should bypass dim or request
another eyes... so I'm just, at least, holding until tomorrow...

> 
> Thanks
> --
> The following changes since commit 279ce5d117078ee8ea40c40199399889981fd808:
> 
>   drm/i915/gvt: declare gvt as i915's soft dependency (2018-07-10 11:13:11 
> +0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-2018-07-17
> 
> for you to fetch changes up to 3e494c2eb417715cdfed66827a5752e41de748c3:
> 
>   drm/i915/gvt: Fix W=1 warnings (2018-07-16 13:28:47 +0800)
> 
> 
> gvt-next-2018-07-17
> 
> - Fix all left W=1 warnings
> 
> 
> Zhenyu Wang (2):
>   drm/i915/gvt: make dma map/unmap kvmgt functions as static
>   drm/i915/gvt: Fix W=1 warnings
> 
>  drivers/gpu/drm/i915/gvt/cfg_space.c| 12 
>  drivers/gpu/drm/i915/gvt/display.c  |  1 +
>  drivers/gpu/drm/i915/gvt/edid.c |  9 +
>  drivers/gpu/drm/i915/gvt/gtt.c  |  9 ++---
>  drivers/gpu/drm/i915/gvt/gvt.c  |  3 +--
>  drivers/gpu/drm/i915/gvt/handlers.c |  1 +
>  drivers/gpu/drm/i915/gvt/kvmgt.c|  4 ++--
>  drivers/gpu/drm/i915/gvt/mmio.c |  3 ++-
>  drivers/gpu/drm/i915/gvt/mmio_context.c | 13 -
>  drivers/gpu/drm/i915/gvt/opregion.c |  1 -
>  drivers/gpu/drm/i915/gvt/page_track.c   |  2 ++
>  drivers/gpu/drm/i915/gvt/reg.h  |  9 +
>  drivers/gpu/drm/i915/gvt/scheduler.c|  4 +++-
>  13 files changed, 48 insertions(+), 23 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

Re: [Intel-gfx] [PULL] gvt-next for 4.19

[Rodrigo Vivi]

On Wed, Jul 11, 2018 at 10:33:53AM +0800, Zhenyu Wang wrote:
> 
> Hi,
> 
> Here's last gvt-next pull for 4.19. Biggest change is to
> add vGPU huge page support for guest, with one BXT fix and
> gvt dependency handling.

Pulled to dinq.

Thanks,
Rodrigo.

> 
> Thanks.
> --
> The following changes since commit 57c8a484a9cbf1315b5299702d12aef04867:
> 
>   drm/i915: Enable KVMGT for BXT. (2018-06-13 10:57:30 +0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-2018-07-11
> 
> for you to fetch changes up to 279ce5d117078ee8ea40c40199399889981fd808:
> 
>   drm/i915/gvt: declare gvt as i915's soft dependency (2018-07-10 11:13:11 
> +0800)
> 
> 
> gvt-next-2018-07-11
> 
> - vGPU huge page support (Changbin)
> - BXT display irq warning fix (Colin)
> - Handle GVT dependency well (Henry)
> 
> 
> Changbin Du (14):
>   drm/i915/gvt: Add new 64K entry type
>   drm/i915/gvt: Add PTE IPS bit operations
>   drm/i915/gvt: Handle MMIO GEN8_GAMW_ECO_DEV_RW_IA for 64K GTT
>   drm/i915/gvt: Detect 64K gtt entry by IPS bit of PDE
>   drm/i915/gvt: Add software PTE flag to mark special 64K splited entry
>   drm/i915/gvt: Add GTT clear_pse operation
>   drm/i915/gvt: Split ppgtt_alloc_spt into two parts
>   drm/i915/gvt: Make PTE iterator 64K entry aware
>   drm/i915/gvt: Add 64K huge gtt support
>   drm/i915/kvmgt: Support setting dma map for huge pages
>   drm/i915/gvt: Add 2M huge gtt support
>   drm/i915/gvt: Handle special sequence on PDE IPS bit
>   drm/i915/gvt: Fix error handling in ppgtt_populate_spt_by_guest_entry
>   drm/i915: Enable platform support for vGPU huge gtt pages
> 
> Colin Xu (1):
>   drm/i915/gvt: Handle EDP_PSR_IMR and EDP_PSR_IIR for BXT.
> 
> Hang Yuan (1):
>   drm/i915/gvt: declare gvt as i915's soft dependency
> 
>  drivers/gpu/drm/i915/gvt/gtt.c   | 423 
> ++-
>  drivers/gpu/drm/i915/gvt/gtt.h   |   9 +
>  drivers/gpu/drm/i915/gvt/gvt.c   |   4 +
>  drivers/gpu/drm/i915/gvt/handlers.c  |  39 +++-
>  drivers/gpu/drm/i915/gvt/hypercall.h |   2 +-
>  drivers/gpu/drm/i915/gvt/kvmgt.c | 126 ---
>  drivers/gpu/drm/i915/gvt/mpt.h   |   7 +-
>  drivers/gpu/drm/i915/gvt/vgpu.c  |   1 +
>  8 files changed, 517 insertions(+), 94 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

Re: [Intel-gfx] [PULL] gvt-next for 4.19

[Zhenyu Wang]

On 2018.07.11 08:45:08 +0100, Chris Wilson wrote:
> Quoting Zhenyu Wang (2018-07-11 03:33:53)
> > 
> > Hi,
> > 
> > Here's last gvt-next pull for 4.19. Biggest change is to
> > add vGPU huge page support for guest, with one BXT fix and
> > gvt dependency handling.
> 
> Any progress to cleaning up all the compiler warnings for W=1?

I'll check all those, thanks for reminding me!

-- 
Open Source Technology Center, Intel ltd.

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


signature.asc
Description: PGP signature
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] [PULL] gvt-next for 4.19

[Chris Wilson]

Quoting Zhenyu Wang (2018-07-11 03:33:53)
> 
> Hi,
> 
> Here's last gvt-next pull for 4.19. Biggest change is to
> add vGPU huge page support for guest, with one BXT fix and
> gvt dependency handling.

Any progress to cleaning up all the compiler warnings for W=1?
-Chris
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Rodrigo Vivi]

On Tue, Jun 19, 2018 at 05:00:43PM +0800, Zhenyu Wang wrote:
> 
> Hi,
> 
> Here is first gvt-next pull for next 4.19 kernel. Mostly on gvt
> optimizations and has added BXT support for GVT-g.

pushed to dinq. Thanks.

> 
> Thanks.
> ---
> The following changes since commit 14c3f8425080a1ff97df7b81f7c339bf42c427a3:
> 
>   drm/i915: Update DRIVER_DATE to 20180606 (2018-06-06 15:10:47 -0700)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-2018-06-19
> 
> for you to fetch changes up to 57c8a484a9cbf1315b5299702d12aef04867:
> 
>   drm/i915: Enable KVMGT for BXT. (2018-06-13 10:57:30 +0800)
> 
> 
> gvt-next-2018-06-19
> 
> - fine-grained per vgpu locking (Colin)
> - fine-grained vgpu scheduler locking (Colin)
> - deliver windows guest cursor hotspot info (Tina)
> - GVT-g BXT support (Colin)
> - other misc and checker fixes (Chris, Xinyun)
> 
> 
> Chris Wilson (1):
>   drm/i915/gvt: Use offsetofend() rather than offsetof + sizeof
> 
> Colin Xu (14):
>   drm/i915/gvt: Use vgpu_lock to protect per vgpu access
>   drm/i915/gvt: Use sched_lock to protect gvt scheduler logic.
>   drm/i915/gvt: Add D_BXT device type define for BXT.
>   drm/i915/gvt: Add MEDIA_POOL_STATE for BXT.
>   drm/i915/gvt: Enable device info initialization for BXT.
>   drm/i915/gvt: Enable gtt initialization for BXT.
>   drm/i915/gvt: Enable irq initialization for BXT.
>   drm/i915/gvt: Enable mmio context init and switch for BXT.
>   drm/i915/gvt: Enable cmd_parser support for BXT.
>   drm/i915/gvt: Enable force wake support for BXT.
>   drm/i915/gvt: Enable virtual display support for BXT.
>   drm/i915/gvt: Enable dma_buf support for BXT.
>   drm/i915/gvt: Add mmio handler for for BXT.
>   drm/i915: Enable KVMGT for BXT.
> 
> Tina Zhang (1):
>   drm/i915/gvt: Deliver guest cursor hotspot info
> 
> Xinyun Liu (3):
>   drm/i915/gvt: Avoid dereference a potential null pointer
>   drm/i915/gvt: removed unnecessary boundary check
>   drm/i915/gvt: use array to avoid potential buffer overflow
> 
> Zhenyu Wang (1):
>   Merge tag 'drm-intel-next-2018-06-06' into gvt-next
> 
>  drivers/gpu/drm/i915/gvt/cmd_parser.c   |  43 ++--
>  drivers/gpu/drm/i915/gvt/display.c  |  58 +++--
>  drivers/gpu/drm/i915/gvt/dmabuf.c   |  26 ++-
>  drivers/gpu/drm/i915/gvt/edid.c |  20 +-
>  drivers/gpu/drm/i915/gvt/execlist.h |  13 +-
>  drivers/gpu/drm/i915/gvt/fb_decoder.c   |  15 +-
>  drivers/gpu/drm/i915/gvt/firmware.c |   2 +-
>  drivers/gpu/drm/i915/gvt/gtt.c  |  11 +-
>  drivers/gpu/drm/i915/gvt/gvt.c  |  27 +--
>  drivers/gpu/drm/i915/gvt/gvt.h  |  16 ++
>  drivers/gpu/drm/i915/gvt/handlers.c | 399 
> 
>  drivers/gpu/drm/i915/gvt/interrupt.c|  17 +-
>  drivers/gpu/drm/i915/gvt/mmio.c |  12 +-
>  drivers/gpu/drm/i915/gvt/mmio.h |  11 +-
>  drivers/gpu/drm/i915/gvt/mmio_context.c |  16 +-
>  drivers/gpu/drm/i915/gvt/page_track.c   |   5 +-
>  drivers/gpu/drm/i915/gvt/sched_policy.c |  36 ++-
>  drivers/gpu/drm/i915/gvt/scheduler.c|  25 +-
>  drivers/gpu/drm/i915/gvt/vgpu.c |  56 ++---
>  drivers/gpu/drm/i915/i915_pvinfo.h  |   5 +-
>  drivers/gpu/drm/i915/intel_gvt.c|   2 +
>  21 files changed, 612 insertions(+), 203 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

Re: [Intel-gfx] [PULL] gvt-next for 4.18

[Wang, Zhi A]

Thanks for the reminder! :)

Thanks,
Zhi.

-Original Message-
From: Nikula, Jani 
Sent: Monday, May 14, 2018 11:36 AM
To: Wang, Zhi A ; Zhenyu Wang ; 
Joonas Lahtinen ; Vivi, Rodrigo 

Cc: intel-gfx ; intel-gvt-dev 
; Lv, Zhiyuan ; 
Yuan, Hang 
Subject: Re: [PULL] gvt-next for 4.18

On Mon, 14 May 2018, Zhi Wang  wrote:
> The following changes since commit 0c79f9cb77eae28d48a4f9fc1b3341aacbbd260c:
>
>drm/i915/gen9: Add WaClearHIZ_WM_CHICKEN3 for bxt and glk 
> (2018-05-13
> 10:29:44 +0100)
>
> are available in the git repository at:
>
>https://github.com/intel/gvt-linux.git tags/gvt-next-2018-05-14
>
> for you to fetch changes up to 41e403d04e7050c8d88682939febcdbe117d4c82:
>
>Revert "drm/i915/gvt: set max priority for gvt context" (2018-05-14
> 05:26:09 +0800)

Pulled, thanks.

Please try to avoid rebases; it looks like you're now the committer for each 
commit but without Signed-off-by.

BR,
Jani.


>
> 
> - Improve the emulation of virtual non-priv register. (Yan)
> - Reverse the hack of host of preemption of GVT-g. (Weinan)
> - Improve untracked warning message.(Changbin)
>
> 
> Changbin Du (1):
>drm/i915/gvt: Remove disable_warn_untrack and print untracked 
> mmio with debug level
>
> Weinan Li (1):
>Revert "drm/i915/gvt: set max priority for gvt context"
>
> Zhao Yan (3):
>drm/i915/gvt: let NOPID be the default value of 
> force_to_nonpriv registers
>drm/i915/gvt: do not return error on handling force_to_nonpriv 
> registers
>drm/i915/gvt: let force_to_nonpriv cmd handler only valid for 
> LRI cmd
>
> Zhi Wang (1):
>Merge branch 'drm-intel-next-queued' into gvt-next
>
>   drivers/gpu/drm/i915/gvt/cmd_parser.c | 26 +-
>   drivers/gpu/drm/i915/gvt/gvt.h|  1 -
>   drivers/gpu/drm/i915/gvt/handlers.c   | 35 
> ++-
>   drivers/gpu/drm/i915/gvt/mmio.c   |  2 --
>   drivers/gpu/drm/i915/gvt/scheduler.c  |  3 ---
>   5 files changed, 39 insertions(+), 28 deletions(-)
>

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

Re: [Intel-gfx] [PULL] gvt-next for 4.18

[Jani Nikula]

On Mon, 14 May 2018, Zhi Wang  wrote:
> The following changes since commit 0c79f9cb77eae28d48a4f9fc1b3341aacbbd260c:
>
>drm/i915/gen9: Add WaClearHIZ_WM_CHICKEN3 for bxt and glk (2018-05-13 
> 10:29:44 +0100)
>
> are available in the git repository at:
>
>https://github.com/intel/gvt-linux.git tags/gvt-next-2018-05-14
>
> for you to fetch changes up to 41e403d04e7050c8d88682939febcdbe117d4c82:
>
>Revert "drm/i915/gvt: set max priority for gvt context" (2018-05-14 
> 05:26:09 +0800)

Pulled, thanks.

Please try to avoid rebases; it looks like you're now the committer for
each commit but without Signed-off-by.

BR,
Jani.


>
> 
> - Improve the emulation of virtual non-priv register. (Yan)
> - Reverse the hack of host of preemption of GVT-g. (Weinan)
> - Improve untracked warning message.(Changbin)
>
> 
> Changbin Du (1):
>drm/i915/gvt: Remove disable_warn_untrack and print untracked 
> mmio with debug level
>
> Weinan Li (1):
>Revert "drm/i915/gvt: set max priority for gvt context"
>
> Zhao Yan (3):
>drm/i915/gvt: let NOPID be the default value of force_to_nonpriv 
> registers
>drm/i915/gvt: do not return error on handling force_to_nonpriv 
> registers
>drm/i915/gvt: let force_to_nonpriv cmd handler only valid for LRI cmd
>
> Zhi Wang (1):
>Merge branch 'drm-intel-next-queued' into gvt-next
>
>   drivers/gpu/drm/i915/gvt/cmd_parser.c | 26 +-
>   drivers/gpu/drm/i915/gvt/gvt.h|  1 -
>   drivers/gpu/drm/i915/gvt/handlers.c   | 35 
> ++-
>   drivers/gpu/drm/i915/gvt/mmio.c   |  2 --
>   drivers/gpu/drm/i915/gvt/scheduler.c  |  3 ---
>   5 files changed, 39 insertions(+), 28 deletions(-)
>

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

Re: [Intel-gfx] [PULL] gvt-next for 4.18

[Zhi Wang]

The patch which causes conflict:

---
From 2e8ea2777af45fe651dbd14b8b8e000e94467c24 Mon Sep 17 00:00:00 2001
From: Weinan Li 
Date: Wed, 21 Mar 2018 15:40:32 +0800
Subject: [PATCH] Revert "drm/i915/gvt: set max priority for gvt context"

This reverts commit 11474e9091cf2002e948647fd9f63a7f027e488a.

There are issues which will block the host preemption before, instead of
disabling it use one workaround "setting max priority for gvt context"
to avoid the gvt context be preempted by the host. Now the issues have been
cleared, so revert this patch to enable host preemption.

v2:
- refine description(Zhenyu)

Signed-off-by: Weinan Li 
Signed-off-by: Zhenyu Wang 
Signed-off-by: Zhi Wang 
---

has a dependency with the following patch which is missing in git tag 
drm-next-intel-2018-04-13:


---
commit b7268c5eed0ab4f052d614b4b0e3fe8a51c9d5a1
Author: Chris Wilson 
Date:   Wed Apr 18 19:40:52 2018 +0100

drm/i915: Pack params to engine->schedule() into a struct

Today we only want to pass along the priority to 
engine->schedule(), but
in the future we want to have much more control over the various 
aspects

of the GPU during a context's execution, for example controlling the
frequency allowed. As we need an ever growing number of parameters for
scheduling, move those into a struct for convenience.

v2: Move the anonymous struct into its own function for legibility and
ye olde gcc.

Signed-off-by: Chris Wilson 
Reviewed-by: Joonas Lahtinen 
Link: 
https://patchwork.freedesktop.org/patch/msgid/20180418184052.7129-3-ch...@chris-wilson.co.uk

---

I found it in drm-tip. Looks I have to send another pull request when 
the patch above is in a new drm-intel-next tag.


Thanks for everyone's efforts.

Thanks,
Zhi.

On 04/23/18 16:13, Zhi Wang wrote:

Hi Jani:

I picked out the patch which causes conflicts and may put it back in the 
next back merge from drm-intel-next to gvt-next. So there shouldn't be 
any conflict in this pull. Thanks for your efforts.


Thanks,
Zhi.

On 04/23/18 16:11, Zhi Wang wrote:
The following changes since commit 
fadec6eefe232696c5c471b40df33e6db616e854:


   drm/i915: Update DRIVER_DATE to 20180413 (2018-04-13 12:20:58 +0300)

are available in the git repository at:

   https://github.com/intel/gvt-linux.git tags/gvt-next-2018-04-23

for you to fetch changes up to 3eda0d22ead04f81ea59c9584bcbf5b496745e92:

   drm/i915/gvt: Mark expected switch fall-through in 
handle_g2v_notification (2018-04-23 13:09:36 +0800)



- Minor condition check improvment (Gustavo A. R. Silva)
- Non-priviliged batch buffer scan (Yan Zhao)
- Scheduling optimizations (Zhipeng Gong)


Gustavo A. R. Silva (2):
   drm/i915/gvt/scheduler: Remove unnecessary NULL checks in 
sr_oa_regs
   drm/i915/gvt: Mark expected switch fall-through in 
handle_g2v_notification


Zhao Yan (1):
   drm/i915/gvt: scan non-privileged batch buffer for debug purpose

Zhipeng Gong (2):
   drm/i915/gvt: Use real time to do timer check
   drm/i915/gvt: Update time slice more frequently

  drivers/gpu/drm/i915/gvt/cmd_parser.c   | 55 
---
  drivers/gpu/drm/i915/gvt/debugfs.c  | 67 
+

  drivers/gpu/drm/i915/gvt/gvt.h  |  1 +
  drivers/gpu/drm/i915/gvt/handlers.c |  1 +
  drivers/gpu/drm/i915/gvt/sched_policy.c | 31 ---
  drivers/gpu/drm/i915/gvt/scheduler.c| 66 
+---

  drivers/gpu/drm/i915/gvt/scheduler.h|  1 +
  drivers/gpu/drm/i915/gvt/trace.h| 24 +---
  8 files changed, 193 insertions(+), 53 deletions(-)


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

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

Re: [Intel-gfx] [PULL] gvt-next for 4.18

[Zhi Wang]

Thanks! :)

On 04/23/18 18:25, Jani Nikula wrote:

On Mon, 23 Apr 2018, Zhi Wang  wrote:

Hi Jani:

I picked out the patch which causes conflicts and may put it back in the
next back merge from drm-intel-next to gvt-next. So there shouldn't be
any conflict in this pull. Thanks for your efforts.


Thanks, pulled to drm-intel-next-queued.

Just as a reminder, if you have more stuff for v4.18 the deadline is in
about three weeks.

BR,
Jani.




Thanks,
Zhi.

On 04/23/18 16:11, Zhi Wang wrote:

The following changes since commit
fadec6eefe232696c5c471b40df33e6db616e854:

drm/i915: Update DRIVER_DATE to 20180413 (2018-04-13 12:20:58 +0300)

are available in the git repository at:

https://github.com/intel/gvt-linux.git tags/gvt-next-2018-04-23

for you to fetch changes up to 3eda0d22ead04f81ea59c9584bcbf5b496745e92:

drm/i915/gvt: Mark expected switch fall-through in
handle_g2v_notification (2018-04-23 13:09:36 +0800)


- Minor condition check improvment (Gustavo A. R. Silva)
- Non-priviliged batch buffer scan (Yan Zhao)
- Scheduling optimizations (Zhipeng Gong)


Gustavo A. R. Silva (2):
drm/i915/gvt/scheduler: Remove unnecessary NULL checks in sr_oa_regs
drm/i915/gvt: Mark expected switch fall-through in
handle_g2v_notification

Zhao Yan (1):
drm/i915/gvt: scan non-privileged batch buffer for debug purpose

Zhipeng Gong (2):
drm/i915/gvt: Use real time to do timer check
drm/i915/gvt: Update time slice more frequently

   drivers/gpu/drm/i915/gvt/cmd_parser.c   | 55 ---
   drivers/gpu/drm/i915/gvt/debugfs.c  | 67
+
   drivers/gpu/drm/i915/gvt/gvt.h  |  1 +
   drivers/gpu/drm/i915/gvt/handlers.c |  1 +
   drivers/gpu/drm/i915/gvt/sched_policy.c | 31 ---
   drivers/gpu/drm/i915/gvt/scheduler.c| 66
+---
   drivers/gpu/drm/i915/gvt/scheduler.h|  1 +
   drivers/gpu/drm/i915/gvt/trace.h| 24 +---
   8 files changed, 193 insertions(+), 53 deletions(-)




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

Re: [Intel-gfx] [PULL] gvt-next for 4.18

[Jani Nikula]

On Mon, 23 Apr 2018, Zhi Wang  wrote:
> Hi Jani:
>
> I picked out the patch which causes conflicts and may put it back in the 
> next back merge from drm-intel-next to gvt-next. So there shouldn't be 
> any conflict in this pull. Thanks for your efforts.

Thanks, pulled to drm-intel-next-queued.

Just as a reminder, if you have more stuff for v4.18 the deadline is in
about three weeks.

BR,
Jani.


>
> Thanks,
> Zhi.
>
> On 04/23/18 16:11, Zhi Wang wrote:
>> The following changes since commit 
>> fadec6eefe232696c5c471b40df33e6db616e854:
>> 
>>drm/i915: Update DRIVER_DATE to 20180413 (2018-04-13 12:20:58 +0300)
>> 
>> are available in the git repository at:
>> 
>>https://github.com/intel/gvt-linux.git tags/gvt-next-2018-04-23
>> 
>> for you to fetch changes up to 3eda0d22ead04f81ea59c9584bcbf5b496745e92:
>> 
>>drm/i915/gvt: Mark expected switch fall-through in 
>> handle_g2v_notification (2018-04-23 13:09:36 +0800)
>> 
>> 
>> - Minor condition check improvment (Gustavo A. R. Silva)
>> - Non-priviliged batch buffer scan (Yan Zhao)
>> - Scheduling optimizations (Zhipeng Gong)
>> 
>> 
>> Gustavo A. R. Silva (2):
>>drm/i915/gvt/scheduler: Remove unnecessary NULL checks in sr_oa_regs
>>drm/i915/gvt: Mark expected switch fall-through in 
>> handle_g2v_notification
>> 
>> Zhao Yan (1):
>>drm/i915/gvt: scan non-privileged batch buffer for debug purpose
>> 
>> Zhipeng Gong (2):
>>drm/i915/gvt: Use real time to do timer check
>>drm/i915/gvt: Update time slice more frequently
>> 
>>   drivers/gpu/drm/i915/gvt/cmd_parser.c   | 55 ---
>>   drivers/gpu/drm/i915/gvt/debugfs.c  | 67 
>> +
>>   drivers/gpu/drm/i915/gvt/gvt.h  |  1 +
>>   drivers/gpu/drm/i915/gvt/handlers.c |  1 +
>>   drivers/gpu/drm/i915/gvt/sched_policy.c | 31 ---
>>   drivers/gpu/drm/i915/gvt/scheduler.c| 66 
>> +---
>>   drivers/gpu/drm/i915/gvt/scheduler.h|  1 +
>>   drivers/gpu/drm/i915/gvt/trace.h| 24 +---
>>   8 files changed, 193 insertions(+), 53 deletions(-)
>> 

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

Re: [Intel-gfx] [PULL] gvt-next for 4.18

[Zhi Wang]

Hi Jani:

I picked out the patch which causes conflicts and may put it back in the 
next back merge from drm-intel-next to gvt-next. So there shouldn't be 
any conflict in this pull. Thanks for your efforts.


Thanks,
Zhi.

On 04/23/18 16:11, Zhi Wang wrote:
The following changes since commit 
fadec6eefe232696c5c471b40df33e6db616e854:


   drm/i915: Update DRIVER_DATE to 20180413 (2018-04-13 12:20:58 +0300)

are available in the git repository at:

   https://github.com/intel/gvt-linux.git tags/gvt-next-2018-04-23

for you to fetch changes up to 3eda0d22ead04f81ea59c9584bcbf5b496745e92:

   drm/i915/gvt: Mark expected switch fall-through in 
handle_g2v_notification (2018-04-23 13:09:36 +0800)



- Minor condition check improvment (Gustavo A. R. Silva)
- Non-priviliged batch buffer scan (Yan Zhao)
- Scheduling optimizations (Zhipeng Gong)


Gustavo A. R. Silva (2):
   drm/i915/gvt/scheduler: Remove unnecessary NULL checks in sr_oa_regs
   drm/i915/gvt: Mark expected switch fall-through in 
handle_g2v_notification


Zhao Yan (1):
   drm/i915/gvt: scan non-privileged batch buffer for debug purpose

Zhipeng Gong (2):
   drm/i915/gvt: Use real time to do timer check
   drm/i915/gvt: Update time slice more frequently

  drivers/gpu/drm/i915/gvt/cmd_parser.c   | 55 ---
  drivers/gpu/drm/i915/gvt/debugfs.c  | 67 
+

  drivers/gpu/drm/i915/gvt/gvt.h  |  1 +
  drivers/gpu/drm/i915/gvt/handlers.c |  1 +
  drivers/gpu/drm/i915/gvt/sched_policy.c | 31 ---
  drivers/gpu/drm/i915/gvt/scheduler.c| 66 
+---

  drivers/gpu/drm/i915/gvt/scheduler.h|  1 +
  drivers/gpu/drm/i915/gvt/trace.h| 24 +---
  8 files changed, 193 insertions(+), 53 deletions(-)


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

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

[Zhi Wang]

Weird. I try to apply the patches one by one on 
drm-intel-next-2018-04-13. I didn't get any conflicts... Let me dig more..


On 04/19/18 17:50, Zhi Wang wrote:
Thanks, Let me discuss with Zhenyu about how to deal with this. It must 
be the git rebase I've done which causes the commiter change without new 
signoff-by.


Thanks,
Zhi.

On 04/19/18 17:34, Jani Nikula wrote:

On Thu, 19 Apr 2018, Zhi Wang  wrote:

Hi:

Here is the pull request of gvt-next for 4.17 with some new features and
optimizations.

Thanks,
Zhi.

--
The following changes since commit 
fadec6eefe232696c5c471b40df33e6db616e854:


drm/i915: Update DRIVER_DATE to 20180413 (2018-04-13 12:20:58 +0300)

are available in the git repository at:

https://github.com/intel/gvt-linux.git tags/gvt-next-2018-04-19

for you to fetch changes up to c0fb4098fc47dcaeb47085c08d8fafa42fa8e471:

drm/i915/gvt: Mark expected switch fall-through in
handle_g2v_notification (2018-04-19 16:35:55 +0800)


- Minor condition check improvment (Gustavo A. R. Silva)
- Reverting GVT context priority hack (Weinan Li)
- Non-priviliged batch buffer scan (Yan Zhao)
- Scheduling optimizations (Zhipeng Gong)


Gustavo A. R. Silva (2):
drm/i915/gvt/scheduler: Remove unnecessary NULL checks in 
sr_oa_regs

drm/i915/gvt: Mark expected switch fall-through in
handle_g2v_notification

Weinan Li (1):
Revert "drm/i915/gvt: set max priority for gvt context"


This reverts a commit in v4.15. Why is it in a -next pull and not a
-fixes pull?

It also conflicts, please advise how to resolve:

diff --cc drivers/gpu/drm/i915/gvt/scheduler.c
index f3d21849b0cb,080fb5027d9c..
--- a/drivers/gpu/drm/i915/gvt/scheduler.c
+++ b/drivers/gpu/drm/i915/gvt/scheduler.c
@@@ -1134,9 -1156,6 +1156,12 @@@ int intel_vgpu_setup_submission(struct
 if (IS_ERR(s->shadow_ctx))
 return PTR_ERR(s->shadow_ctx);
++<<< HEAD
  +  if (HAS_LOGICAL_RING_PREEMPTION(vgpu->gvt->dev_priv))
  +  s->shadow_ctx->sched.priority = INT_MAX;
  +
++===
++>>> c2f6410ef67740ebcbf5d92dffc2679d4a0e288c
 bitmap_zero(s->shadow_ctx_desc_updated, I915_NUM_ENGINES);
 s->workloads = kmem_cache_create_usercopy("gvt-g_vgpu_workload",

Finally, it's committed by Zhi Wang  but without
his Signed-off-by.


BR,
Jani.




Zhao Yan (1):
drm/i915/gvt: scan non-privileged batch buffer for debug purpose

Zhipeng Gong (2):
drm/i915/gvt: Use real time to do timer check
drm/i915/gvt: Update time slice more frequently

   drivers/gpu/drm/i915/gvt/cmd_parser.c   | 55 
+++---

   drivers/gpu/drm/i915/gvt/debugfs.c  | 67

   drivers/gpu/drm/i915/gvt/gvt.h  |  1 +
   drivers/gpu/drm/i915/gvt/handlers.c |  1 +
   drivers/gpu/drm/i915/gvt/sched_policy.c | 31 ---
   drivers/gpu/drm/i915/gvt/scheduler.c| 69
+
   drivers/gpu/drm/i915/gvt/scheduler.h|  1 +
   drivers/gpu/drm/i915/gvt/trace.h| 24 +---
   8 files changed, 193 insertions(+), 56 deletions(-)



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

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

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

[Zhenyu Wang]

On 2018.04.19 12:34:16 +0300, Jani Nikula wrote:
> On Thu, 19 Apr 2018, Zhi Wang  wrote:
> > Hi:
> >
> > Here is the pull request of gvt-next for 4.17 with some new features and 
> > optimizations.
> >
> > Thanks,
> > Zhi.
> >
> > --
> > The following changes since commit fadec6eefe232696c5c471b40df33e6db616e854:
> >
> >drm/i915: Update DRIVER_DATE to 20180413 (2018-04-13 12:20:58 +0300)
> >
> > are available in the git repository at:
> >
> >https://github.com/intel/gvt-linux.git tags/gvt-next-2018-04-19
> >
> > for you to fetch changes up to c0fb4098fc47dcaeb47085c08d8fafa42fa8e471:
> >
> >drm/i915/gvt: Mark expected switch fall-through in 
> > handle_g2v_notification (2018-04-19 16:35:55 +0800)
> >
> > 
> > - Minor condition check improvment (Gustavo A. R. Silva)
> > - Reverting GVT context priority hack (Weinan Li)
> > - Non-priviliged batch buffer scan (Yan Zhao)
> > - Scheduling optimizations (Zhipeng Gong)
> >
> > 
> > Gustavo A. R. Silva (2):
> >drm/i915/gvt/scheduler: Remove unnecessary NULL checks in sr_oa_regs
> >drm/i915/gvt: Mark expected switch fall-through in 
> > handle_g2v_notification
> >
> > Weinan Li (1):
> >Revert "drm/i915/gvt: set max priority for gvt context"
> 
> This reverts a commit in v4.15. Why is it in a -next pull and not a
> -fixes pull?

This one was originally queued for 4.17 in gvt-next-fixes, but declined as
Joonas thought this is new feature as enabling vGPU priority scheduling,
https://lists.freedesktop.org/archives/intel-gfx/2018-March/160431.html

> 
> It also conflicts, please advise how to resolve:
> 
> diff --cc drivers/gpu/drm/i915/gvt/scheduler.c
> index f3d21849b0cb,080fb5027d9c..
> --- a/drivers/gpu/drm/i915/gvt/scheduler.c
> +++ b/drivers/gpu/drm/i915/gvt/scheduler.c
> @@@ -1134,9 -1156,6 +1156,12 @@@ int intel_vgpu_setup_submission(struct 
> if (IS_ERR(s->shadow_ctx))
> return PTR_ERR(s->shadow_ctx);
>   
> ++<<< HEAD
>  +  if (HAS_LOGICAL_RING_PREEMPTION(vgpu->gvt->dev_priv))
>  +  s->shadow_ctx->sched.priority = INT_MAX;
>  +
> ++===
> ++>>> c2f6410ef67740ebcbf5d92dffc2679d4a0e288c
> bitmap_zero(s->shadow_ctx_desc_updated, I915_NUM_ENGINES);
>   
> s->workloads = kmem_cache_create_usercopy("gvt-g_vgpu_workload",
> 
> Finally, it's committed by Zhi Wang  but without
> his Signed-off-by.
> 
> 
> BR,
> Jani.
> 
> 
> >
> > Zhao Yan (1):
> >drm/i915/gvt: scan non-privileged batch buffer for debug purpose
> >
> > Zhipeng Gong (2):
> >drm/i915/gvt: Use real time to do timer check
> >drm/i915/gvt: Update time slice more frequently
> >
> >   drivers/gpu/drm/i915/gvt/cmd_parser.c   | 55 +++---
> >   drivers/gpu/drm/i915/gvt/debugfs.c  | 67 
> > 
> >   drivers/gpu/drm/i915/gvt/gvt.h  |  1 +
> >   drivers/gpu/drm/i915/gvt/handlers.c |  1 +
> >   drivers/gpu/drm/i915/gvt/sched_policy.c | 31 ---
> >   drivers/gpu/drm/i915/gvt/scheduler.c| 69 
> > +
> >   drivers/gpu/drm/i915/gvt/scheduler.h|  1 +
> >   drivers/gpu/drm/i915/gvt/trace.h| 24 +---
> >   8 files changed, 193 insertions(+), 56 deletions(-)
> 
> -- 
> Jani Nikula, Intel Open Source Technology Center

-- 
Open Source Technology Center, Intel ltd.

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


signature.asc
Description: PGP signature
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

[Zhi Wang]

Thanks, Let me discuss with Zhenyu about how to deal with this. It must 
be the git rebase I've done which causes the commiter change without new 
signoff-by.


Thanks,
Zhi.

On 04/19/18 17:34, Jani Nikula wrote:

On Thu, 19 Apr 2018, Zhi Wang  wrote:

Hi:

Here is the pull request of gvt-next for 4.17 with some new features and
optimizations.

Thanks,
Zhi.

--
The following changes since commit fadec6eefe232696c5c471b40df33e6db616e854:

drm/i915: Update DRIVER_DATE to 20180413 (2018-04-13 12:20:58 +0300)

are available in the git repository at:

https://github.com/intel/gvt-linux.git tags/gvt-next-2018-04-19

for you to fetch changes up to c0fb4098fc47dcaeb47085c08d8fafa42fa8e471:

drm/i915/gvt: Mark expected switch fall-through in
handle_g2v_notification (2018-04-19 16:35:55 +0800)


- Minor condition check improvment (Gustavo A. R. Silva)
- Reverting GVT context priority hack (Weinan Li)
- Non-priviliged batch buffer scan (Yan Zhao)
- Scheduling optimizations (Zhipeng Gong)


Gustavo A. R. Silva (2):
drm/i915/gvt/scheduler: Remove unnecessary NULL checks in sr_oa_regs
drm/i915/gvt: Mark expected switch fall-through in
handle_g2v_notification

Weinan Li (1):
Revert "drm/i915/gvt: set max priority for gvt context"


This reverts a commit in v4.15. Why is it in a -next pull and not a
-fixes pull?

It also conflicts, please advise how to resolve:

diff --cc drivers/gpu/drm/i915/gvt/scheduler.c
index f3d21849b0cb,080fb5027d9c..
--- a/drivers/gpu/drm/i915/gvt/scheduler.c
+++ b/drivers/gpu/drm/i915/gvt/scheduler.c
@@@ -1134,9 -1156,6 +1156,12 @@@ int intel_vgpu_setup_submission(struct
 if (IS_ERR(s->shadow_ctx))
 return PTR_ERR(s->shadow_ctx);
   
++<<< HEAD

  +  if (HAS_LOGICAL_RING_PREEMPTION(vgpu->gvt->dev_priv))
  +  s->shadow_ctx->sched.priority = INT_MAX;
  +
++===
++>>> c2f6410ef67740ebcbf5d92dffc2679d4a0e288c
 bitmap_zero(s->shadow_ctx_desc_updated, I915_NUM_ENGINES);
   
 s->workloads = kmem_cache_create_usercopy("gvt-g_vgpu_workload",


Finally, it's committed by Zhi Wang  but without
his Signed-off-by.


BR,
Jani.




Zhao Yan (1):
drm/i915/gvt: scan non-privileged batch buffer for debug purpose

Zhipeng Gong (2):
drm/i915/gvt: Use real time to do timer check
drm/i915/gvt: Update time slice more frequently

   drivers/gpu/drm/i915/gvt/cmd_parser.c   | 55 +++---
   drivers/gpu/drm/i915/gvt/debugfs.c  | 67

   drivers/gpu/drm/i915/gvt/gvt.h  |  1 +
   drivers/gpu/drm/i915/gvt/handlers.c |  1 +
   drivers/gpu/drm/i915/gvt/sched_policy.c | 31 ---
   drivers/gpu/drm/i915/gvt/scheduler.c| 69
+
   drivers/gpu/drm/i915/gvt/scheduler.h|  1 +
   drivers/gpu/drm/i915/gvt/trace.h| 24 +---
   8 files changed, 193 insertions(+), 56 deletions(-)



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

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

[Jani Nikula]

On Thu, 19 Apr 2018, Zhi Wang  wrote:
> Hi:
>
> Here is the pull request of gvt-next for 4.17 with some new features and 
> optimizations.
>
> Thanks,
> Zhi.
>
> --
> The following changes since commit fadec6eefe232696c5c471b40df33e6db616e854:
>
>drm/i915: Update DRIVER_DATE to 20180413 (2018-04-13 12:20:58 +0300)
>
> are available in the git repository at:
>
>https://github.com/intel/gvt-linux.git tags/gvt-next-2018-04-19
>
> for you to fetch changes up to c0fb4098fc47dcaeb47085c08d8fafa42fa8e471:
>
>drm/i915/gvt: Mark expected switch fall-through in 
> handle_g2v_notification (2018-04-19 16:35:55 +0800)
>
> 
> - Minor condition check improvment (Gustavo A. R. Silva)
> - Reverting GVT context priority hack (Weinan Li)
> - Non-priviliged batch buffer scan (Yan Zhao)
> - Scheduling optimizations (Zhipeng Gong)
>
> 
> Gustavo A. R. Silva (2):
>drm/i915/gvt/scheduler: Remove unnecessary NULL checks in sr_oa_regs
>drm/i915/gvt: Mark expected switch fall-through in 
> handle_g2v_notification
>
> Weinan Li (1):
>Revert "drm/i915/gvt: set max priority for gvt context"

This reverts a commit in v4.15. Why is it in a -next pull and not a
-fixes pull?

It also conflicts, please advise how to resolve:

diff --cc drivers/gpu/drm/i915/gvt/scheduler.c
index f3d21849b0cb,080fb5027d9c..
--- a/drivers/gpu/drm/i915/gvt/scheduler.c
+++ b/drivers/gpu/drm/i915/gvt/scheduler.c
@@@ -1134,9 -1156,6 +1156,12 @@@ int intel_vgpu_setup_submission(struct 
if (IS_ERR(s->shadow_ctx))
return PTR_ERR(s->shadow_ctx);
  
++<<< HEAD
 +  if (HAS_LOGICAL_RING_PREEMPTION(vgpu->gvt->dev_priv))
 +  s->shadow_ctx->sched.priority = INT_MAX;
 +
++===
++>>> c2f6410ef67740ebcbf5d92dffc2679d4a0e288c
bitmap_zero(s->shadow_ctx_desc_updated, I915_NUM_ENGINES);
  
s->workloads = kmem_cache_create_usercopy("gvt-g_vgpu_workload",

Finally, it's committed by Zhi Wang  but without
his Signed-off-by.


BR,
Jani.


>
> Zhao Yan (1):
>drm/i915/gvt: scan non-privileged batch buffer for debug purpose
>
> Zhipeng Gong (2):
>drm/i915/gvt: Use real time to do timer check
>drm/i915/gvt: Update time slice more frequently
>
>   drivers/gpu/drm/i915/gvt/cmd_parser.c   | 55 +++---
>   drivers/gpu/drm/i915/gvt/debugfs.c  | 67 
> 
>   drivers/gpu/drm/i915/gvt/gvt.h  |  1 +
>   drivers/gpu/drm/i915/gvt/handlers.c |  1 +
>   drivers/gpu/drm/i915/gvt/sched_policy.c | 31 ---
>   drivers/gpu/drm/i915/gvt/scheduler.c| 69 
> +
>   drivers/gpu/drm/i915/gvt/scheduler.h|  1 +
>   drivers/gpu/drm/i915/gvt/trace.h| 24 +---
>   8 files changed, 193 insertions(+), 56 deletions(-)

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

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

[Zhi Wang]

Sorry it's gvt-next, so it should be for 4.18.

Thanks,
Zhi.

On 04/19/18 17:17, Zhi Wang wrote:

Hi:

Here is the pull request of gvt-next for 4.17 with some new features and 
optimizations.


Thanks,
Zhi.

--
The following changes since commit 
fadec6eefe232696c5c471b40df33e6db616e854:


   drm/i915: Update DRIVER_DATE to 20180413 (2018-04-13 12:20:58 +0300)

are available in the git repository at:

   https://github.com/intel/gvt-linux.git tags/gvt-next-2018-04-19

for you to fetch changes up to c0fb4098fc47dcaeb47085c08d8fafa42fa8e471:

   drm/i915/gvt: Mark expected switch fall-through in 
handle_g2v_notification (2018-04-19 16:35:55 +0800)



- Minor condition check improvment (Gustavo A. R. Silva)
- Reverting GVT context priority hack (Weinan Li)
- Non-priviliged batch buffer scan (Yan Zhao)
- Scheduling optimizations (Zhipeng Gong)


Gustavo A. R. Silva (2):
   drm/i915/gvt/scheduler: Remove unnecessary NULL checks in sr_oa_regs
   drm/i915/gvt: Mark expected switch fall-through in 
handle_g2v_notification


Weinan Li (1):
   Revert "drm/i915/gvt: set max priority for gvt context"

Zhao Yan (1):
   drm/i915/gvt: scan non-privileged batch buffer for debug purpose

Zhipeng Gong (2):
   drm/i915/gvt: Use real time to do timer check
   drm/i915/gvt: Update time slice more frequently

  drivers/gpu/drm/i915/gvt/cmd_parser.c   | 55 +++---
  drivers/gpu/drm/i915/gvt/debugfs.c  | 67 


  drivers/gpu/drm/i915/gvt/gvt.h  |  1 +
  drivers/gpu/drm/i915/gvt/handlers.c |  1 +
  drivers/gpu/drm/i915/gvt/sched_policy.c | 31 ---
  drivers/gpu/drm/i915/gvt/scheduler.c| 69 
+

  drivers/gpu/drm/i915/gvt/scheduler.h|  1 +
  drivers/gpu/drm/i915/gvt/trace.h| 24 +---
  8 files changed, 193 insertions(+), 56 deletions(-)
___
intel-gvt-dev mailing list
intel-gvt-...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev

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

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

[Joonas Lahtinen]

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

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

[Joonas Lahtinen]

Quoting Jani Nikula (2018-03-09 12:30:13)
> 
> Joonas, so did this miss the deadline for v4.17? You're not making
> another pull request?

As discussed in the IRC, it got merged. Only in the final pull request
generation I'll summarize all the intermediate tags.

Regards, Joonas

> 
> BR,
> Jani.
> 
> On Thu, 08 Mar 2018, Joonas Lahtinen  wrote:
> > Pulled.
> >
> > Regards, Joonas
> >
> > Quoting Zhenyu Wang (2018-03-08 04:31:52)
> >> 
> >> Hi,
> >> 
> >> Here's gvt-next update for 4.17. Biggest update is for huge code
> >> refactor of shadow ppgtt from Changbin which is the most obscured
> >> part, and with KBL context save/restore improvement from Weinan,
> >> with other fixes.
> >> 
> >> Thanks.
> >> --
> >> The following changes since commit 
> >> 1f267a572b573b0b155022750cba93001f4367a8:
> >> 
> >>   drm/i915: Update DRIVER_DATE to 20180305 (2018-03-05 11:56:15 +0200)
> >> 
> >> are available in the Git repository at:
> >> 
> >>   https://github.com/intel/gvt-linux.git tags/gvt-next-2018-03-08
> >> 
> >> for you to fetch changes up to 991ecefbdd4b81719597d6c406df8d26ef5c1546:
> >> 
> >>   drm/i915/gvt: Return error at the failure of finding page_track 
> >> (2018-03-06 14:49:38 +0800)
> >> 
> >> 
> >> gvt-next-2018-03-08
> >> 
> >> - big refactor for shadow ppgtt (Changbin)
> >> - KBL context save/restore via LRI cmd (Weinan)
> >> - misc smatch fixes (Zhenyu)
> >> - Properly unmap dma for guest page (Changbin)
> >> - other misc fixes (Xiong, etc.)
> >> 
> >> 
> >> Changbin Du (18):
> >>   drm/i915/gvt: Rework shadow graphic memory management code
> >>   drm/i915/gvt: Refine the intel_vgpu_mm reference management
> >>   drm/i915/gvt: Refine ggtt and ppgtt root entry ops
> >>   drm/i915/gvt: Refine ggtt_set_shadow_entry
> >>   drm/i915/gvt: Add verbose gtt shadow logs
> >>   drm/i915/gvt: Rename ggtt related functions to be more specific
> >>   drm/i915/gvt: Factor out intel_vgpu_{get, put}_ppgtt_mm interface
> >>   drm/i915/gvt: Use standard pte bit definition
> >>   drm/i915/gvt: Refine pte shadowing process
> >>   drm/i915/gvt: Rework shadow page management code
> >>   drm/i915/gvt: Rename shadow_page to short name spt
> >>   drm/i915/gvt: Rename mpt api {set, unset}_wp_page to {enable, 
> >> disable}_page_track
> >>   drm/i915/gvt: Don't extend page_track to mpt layer
> >>   drm/i915/gvt: Provide generic page_track infrastructure for 
> >> write-protected page
> >>   drm/i915/gvt: Manage shadow pages with radix tree
> >>   drm/i915/gvt: Define PTE addr mask with GENMASK_ULL
> >>   drm/i915/gvt: Fix guest vGPU hang caused by very high dma setup 
> >> overhead
> >>   drm/i915/kvmgt: Add kvmgt debugfs entry nr_cache_entries under vgpu
> >> 
> >> Weinan Li (3):
> >>   drm/i915/gvt: add define GEN9_MOCS_SIZE
> >>   drm/i915/gvt: add interface to check if context is inhibit
> >>   drm/i915/gvt: init mmio by lri command in vgpu inhibit context
> >> 
> >> Xiong Zhang (2):
> >>   drm/i915/gvt: Release gvt->lock at the failure of finding page track
> >>   drm/i915/gvt: Return error at the failure of finding page_track
> >> 
> >> Zhenyu Wang (7):
> >>   drm/i915/gvt: Fix one gvt_vgpu_error() use in dmabuf.c
> >>   drm/i915/gvt: remove gvt max port definition
> >>   drm/i915/gvt: Fix vGPU sched timeslice calculation warning
> >>   drm/i915/gvt: Fix check error of vgpu create failure message
> >>   drm/i915/gvt: Fix check error on fence mmio handler
> >>   drm/i915/gvt: Fix one indent error
> >>   drm/i915/gvt: Fix check error on hws_pga_write() fail message
> >> 
> >>  drivers/gpu/drm/i915/gvt/Makefile   |2 +-
> >>  drivers/gpu/drm/i915/gvt/dmabuf.c   |2 +-
> >>  drivers/gpu/drm/i915/gvt/gtt.c  | 1457 
> >> ++-
> >>  drivers/gpu/drm/i915/gvt/gtt.h  |  189 ++--
> >>  drivers/gpu/drm/i915/gvt/gvt.c  |2 +-
> >>  drivers/gpu/drm/i915/gvt/gvt.h  |   21 +-
> >>  drivers/gpu/drm/i915/gvt/handlers.c |   38 +-
> >>  drivers/gpu/drm/i915/gvt/hypercall.h|9 +-
> >>  drivers/gpu/drm/i915/gvt/kvmgt.c|  313 ---
> >>  drivers/gpu/drm/i915/gvt/mmio.c |9 +-
> >>  drivers/gpu/drm/i915/gvt/mmio_context.c |  210 -
> >>  drivers/gpu/drm/i915/gvt/mmio_context.h |5 +
> >>  drivers/gpu/drm/i915/gvt/mpt.h  |   67 +-
> >>  drivers/gpu/drm/i915/gvt/page_track.c   |  184 
> >>  drivers/gpu/drm/i915/gvt/page_track.h   |   56 ++
> >>  drivers/gpu/drm/i915/gvt/sched_policy.c |5 +-
> >>  drivers/gpu/drm/i915/gvt/scheduler.c|   44 +-
> >>  drivers/gpu/drm/i915/gvt/trace.h|   10 +-
> >>  drivers/gpu/drm/i915/gvt/vgpu.c |1 +
> >>  19 files changed, 1468 insertions(+), 1156 deletions(-)
> >>  create mode 

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

[Jani Nikula]

Joonas, so did this miss the deadline for v4.17? You're not making
another pull request?

BR,
Jani.

On Thu, 08 Mar 2018, Joonas Lahtinen  wrote:
> Pulled.
>
> Regards, Joonas
>
> Quoting Zhenyu Wang (2018-03-08 04:31:52)
>> 
>> Hi,
>> 
>> Here's gvt-next update for 4.17. Biggest update is for huge code
>> refactor of shadow ppgtt from Changbin which is the most obscured
>> part, and with KBL context save/restore improvement from Weinan,
>> with other fixes.
>> 
>> Thanks.
>> --
>> The following changes since commit 1f267a572b573b0b155022750cba93001f4367a8:
>> 
>>   drm/i915: Update DRIVER_DATE to 20180305 (2018-03-05 11:56:15 +0200)
>> 
>> are available in the Git repository at:
>> 
>>   https://github.com/intel/gvt-linux.git tags/gvt-next-2018-03-08
>> 
>> for you to fetch changes up to 991ecefbdd4b81719597d6c406df8d26ef5c1546:
>> 
>>   drm/i915/gvt: Return error at the failure of finding page_track 
>> (2018-03-06 14:49:38 +0800)
>> 
>> 
>> gvt-next-2018-03-08
>> 
>> - big refactor for shadow ppgtt (Changbin)
>> - KBL context save/restore via LRI cmd (Weinan)
>> - misc smatch fixes (Zhenyu)
>> - Properly unmap dma for guest page (Changbin)
>> - other misc fixes (Xiong, etc.)
>> 
>> 
>> Changbin Du (18):
>>   drm/i915/gvt: Rework shadow graphic memory management code
>>   drm/i915/gvt: Refine the intel_vgpu_mm reference management
>>   drm/i915/gvt: Refine ggtt and ppgtt root entry ops
>>   drm/i915/gvt: Refine ggtt_set_shadow_entry
>>   drm/i915/gvt: Add verbose gtt shadow logs
>>   drm/i915/gvt: Rename ggtt related functions to be more specific
>>   drm/i915/gvt: Factor out intel_vgpu_{get, put}_ppgtt_mm interface
>>   drm/i915/gvt: Use standard pte bit definition
>>   drm/i915/gvt: Refine pte shadowing process
>>   drm/i915/gvt: Rework shadow page management code
>>   drm/i915/gvt: Rename shadow_page to short name spt
>>   drm/i915/gvt: Rename mpt api {set, unset}_wp_page to {enable, 
>> disable}_page_track
>>   drm/i915/gvt: Don't extend page_track to mpt layer
>>   drm/i915/gvt: Provide generic page_track infrastructure for 
>> write-protected page
>>   drm/i915/gvt: Manage shadow pages with radix tree
>>   drm/i915/gvt: Define PTE addr mask with GENMASK_ULL
>>   drm/i915/gvt: Fix guest vGPU hang caused by very high dma setup 
>> overhead
>>   drm/i915/kvmgt: Add kvmgt debugfs entry nr_cache_entries under vgpu
>> 
>> Weinan Li (3):
>>   drm/i915/gvt: add define GEN9_MOCS_SIZE
>>   drm/i915/gvt: add interface to check if context is inhibit
>>   drm/i915/gvt: init mmio by lri command in vgpu inhibit context
>> 
>> Xiong Zhang (2):
>>   drm/i915/gvt: Release gvt->lock at the failure of finding page track
>>   drm/i915/gvt: Return error at the failure of finding page_track
>> 
>> Zhenyu Wang (7):
>>   drm/i915/gvt: Fix one gvt_vgpu_error() use in dmabuf.c
>>   drm/i915/gvt: remove gvt max port definition
>>   drm/i915/gvt: Fix vGPU sched timeslice calculation warning
>>   drm/i915/gvt: Fix check error of vgpu create failure message
>>   drm/i915/gvt: Fix check error on fence mmio handler
>>   drm/i915/gvt: Fix one indent error
>>   drm/i915/gvt: Fix check error on hws_pga_write() fail message
>> 
>>  drivers/gpu/drm/i915/gvt/Makefile   |2 +-
>>  drivers/gpu/drm/i915/gvt/dmabuf.c   |2 +-
>>  drivers/gpu/drm/i915/gvt/gtt.c  | 1457 
>> ++-
>>  drivers/gpu/drm/i915/gvt/gtt.h  |  189 ++--
>>  drivers/gpu/drm/i915/gvt/gvt.c  |2 +-
>>  drivers/gpu/drm/i915/gvt/gvt.h  |   21 +-
>>  drivers/gpu/drm/i915/gvt/handlers.c |   38 +-
>>  drivers/gpu/drm/i915/gvt/hypercall.h|9 +-
>>  drivers/gpu/drm/i915/gvt/kvmgt.c|  313 ---
>>  drivers/gpu/drm/i915/gvt/mmio.c |9 +-
>>  drivers/gpu/drm/i915/gvt/mmio_context.c |  210 -
>>  drivers/gpu/drm/i915/gvt/mmio_context.h |5 +
>>  drivers/gpu/drm/i915/gvt/mpt.h  |   67 +-
>>  drivers/gpu/drm/i915/gvt/page_track.c   |  184 
>>  drivers/gpu/drm/i915/gvt/page_track.h   |   56 ++
>>  drivers/gpu/drm/i915/gvt/sched_policy.c |5 +-
>>  drivers/gpu/drm/i915/gvt/scheduler.c|   44 +-
>>  drivers/gpu/drm/i915/gvt/trace.h|   10 +-
>>  drivers/gpu/drm/i915/gvt/vgpu.c |1 +
>>  19 files changed, 1468 insertions(+), 1156 deletions(-)
>>  create mode 100644 drivers/gpu/drm/i915/gvt/page_track.c
>>  create mode 100644 drivers/gpu/drm/i915/gvt/page_track.h
>> 
>> 
>> -- 
>> Open Source Technology Center, Intel ltd.
>> 
>> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

-- 
Jani Nikula, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org

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

[Joonas Lahtinen]

Pulled.

Regards, Joonas

Quoting Zhenyu Wang (2018-03-08 04:31:52)
> 
> Hi,
> 
> Here's gvt-next update for 4.17. Biggest update is for huge code
> refactor of shadow ppgtt from Changbin which is the most obscured
> part, and with KBL context save/restore improvement from Weinan,
> with other fixes.
> 
> Thanks.
> --
> The following changes since commit 1f267a572b573b0b155022750cba93001f4367a8:
> 
>   drm/i915: Update DRIVER_DATE to 20180305 (2018-03-05 11:56:15 +0200)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-2018-03-08
> 
> for you to fetch changes up to 991ecefbdd4b81719597d6c406df8d26ef5c1546:
> 
>   drm/i915/gvt: Return error at the failure of finding page_track (2018-03-06 
> 14:49:38 +0800)
> 
> 
> gvt-next-2018-03-08
> 
> - big refactor for shadow ppgtt (Changbin)
> - KBL context save/restore via LRI cmd (Weinan)
> - misc smatch fixes (Zhenyu)
> - Properly unmap dma for guest page (Changbin)
> - other misc fixes (Xiong, etc.)
> 
> 
> Changbin Du (18):
>   drm/i915/gvt: Rework shadow graphic memory management code
>   drm/i915/gvt: Refine the intel_vgpu_mm reference management
>   drm/i915/gvt: Refine ggtt and ppgtt root entry ops
>   drm/i915/gvt: Refine ggtt_set_shadow_entry
>   drm/i915/gvt: Add verbose gtt shadow logs
>   drm/i915/gvt: Rename ggtt related functions to be more specific
>   drm/i915/gvt: Factor out intel_vgpu_{get, put}_ppgtt_mm interface
>   drm/i915/gvt: Use standard pte bit definition
>   drm/i915/gvt: Refine pte shadowing process
>   drm/i915/gvt: Rework shadow page management code
>   drm/i915/gvt: Rename shadow_page to short name spt
>   drm/i915/gvt: Rename mpt api {set, unset}_wp_page to {enable, 
> disable}_page_track
>   drm/i915/gvt: Don't extend page_track to mpt layer
>   drm/i915/gvt: Provide generic page_track infrastructure for 
> write-protected page
>   drm/i915/gvt: Manage shadow pages with radix tree
>   drm/i915/gvt: Define PTE addr mask with GENMASK_ULL
>   drm/i915/gvt: Fix guest vGPU hang caused by very high dma setup overhead
>   drm/i915/kvmgt: Add kvmgt debugfs entry nr_cache_entries under vgpu
> 
> Weinan Li (3):
>   drm/i915/gvt: add define GEN9_MOCS_SIZE
>   drm/i915/gvt: add interface to check if context is inhibit
>   drm/i915/gvt: init mmio by lri command in vgpu inhibit context
> 
> Xiong Zhang (2):
>   drm/i915/gvt: Release gvt->lock at the failure of finding page track
>   drm/i915/gvt: Return error at the failure of finding page_track
> 
> Zhenyu Wang (7):
>   drm/i915/gvt: Fix one gvt_vgpu_error() use in dmabuf.c
>   drm/i915/gvt: remove gvt max port definition
>   drm/i915/gvt: Fix vGPU sched timeslice calculation warning
>   drm/i915/gvt: Fix check error of vgpu create failure message
>   drm/i915/gvt: Fix check error on fence mmio handler
>   drm/i915/gvt: Fix one indent error
>   drm/i915/gvt: Fix check error on hws_pga_write() fail message
> 
>  drivers/gpu/drm/i915/gvt/Makefile   |2 +-
>  drivers/gpu/drm/i915/gvt/dmabuf.c   |2 +-
>  drivers/gpu/drm/i915/gvt/gtt.c  | 1457 
> ++-
>  drivers/gpu/drm/i915/gvt/gtt.h  |  189 ++--
>  drivers/gpu/drm/i915/gvt/gvt.c  |2 +-
>  drivers/gpu/drm/i915/gvt/gvt.h  |   21 +-
>  drivers/gpu/drm/i915/gvt/handlers.c |   38 +-
>  drivers/gpu/drm/i915/gvt/hypercall.h|9 +-
>  drivers/gpu/drm/i915/gvt/kvmgt.c|  313 ---
>  drivers/gpu/drm/i915/gvt/mmio.c |9 +-
>  drivers/gpu/drm/i915/gvt/mmio_context.c |  210 -
>  drivers/gpu/drm/i915/gvt/mmio_context.h |5 +
>  drivers/gpu/drm/i915/gvt/mpt.h  |   67 +-
>  drivers/gpu/drm/i915/gvt/page_track.c   |  184 
>  drivers/gpu/drm/i915/gvt/page_track.h   |   56 ++
>  drivers/gpu/drm/i915/gvt/sched_policy.c |5 +-
>  drivers/gpu/drm/i915/gvt/scheduler.c|   44 +-
>  drivers/gpu/drm/i915/gvt/trace.h|   10 +-
>  drivers/gpu/drm/i915/gvt/vgpu.c |1 +
>  19 files changed, 1468 insertions(+), 1156 deletions(-)
>  create mode 100644 drivers/gpu/drm/i915/gvt/page_track.c
>  create mode 100644 drivers/gpu/drm/i915/gvt/page_track.h
> 
> 
> -- 
> 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