intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
	"Vetter, Daniel" <daniel.vetter@intel.com>,
	Dave Airlie <airlied@gmail.com>
Cc: "Zhao, Yan Y" <yan.y.zhao@intel.com>,
	Jani Nikula <jani.nikula@intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	"Yuan, Hang" <hang.yuan@intel.com>,
	"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
	intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PULL] gvt-next-fixes
Date: Fri, 3 Apr 2020 10:50:33 -0700	[thread overview]
Message-ID: <20200403175033.GA3997092@intel.com> (raw)
In-Reply-To: <20200403030507.GQ16629@zhen-hp.sh.intel.com>


+Dave and Daniel,

On Fri, Apr 03, 2020 at 11:05:07AM +0800, Zhenyu Wang wrote:
> On 2020.03.31 09:26:44 -0700, Rodrigo Vivi wrote:
> > On Tue, Mar 31, 2020 at 03:00:25PM +0800, Zhenyu Wang wrote:
> > > 
> > > Hi,
> > > 
> > > Here's more queued gvt fixes for 5.7. Please see details below.
> > > 
> > > Thanks
> > > --
> > > The following changes since commit a61ac1e75105a077ec1efd6923ae3c619f862304:
> > > 
> > >   drm/i915/gvt: Wean gvt off using dev_priv (2020-03-06 10:08:10 +0800)
> > > 
> > > are available in the Git repository at:
> > > 
> > >   https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2020-03-31
> > > 
> > > for you to fetch changes up to eb0ff8074e0baecba2cd0c7813f6cfa99bafc430:
> > > 
> > >   drm/i915/gvt: Fix klocwork issues about data size (2020-03-27 15:37:58 +0800)
> > 
> > pulled, thanks
> 
> I forgot to mention one thing for 5.7. We've fixed to change guest mem r/w
> from KVM to use new VFIO dma r/w instead in this series: https://patchwork.freedesktop.org/series/72038/
> 
> As this depends on VFIO tree and looks VFIO pull for 5.7 is not settled down
> yet, we'd need to backmerge and send pull against vfio merge for 5.7.

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

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

Is that what you want?

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



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

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

  reply	other threads:[~2020-04-03 17:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31  7:00 [Intel-gfx] [PULL] gvt-next-fixes Zhenyu Wang
2020-03-31 16:26 ` Rodrigo Vivi
2020-04-03  3:05   ` Zhenyu Wang
2020-04-03 17:50     ` Rodrigo Vivi [this message]
2020-04-07  8:02       ` Zhenyu Wang
2020-04-07 13:35         ` Rodrigo Vivi
2020-04-07 13:53           ` Jani Nikula
2020-04-07 23:36             ` Zhenyu Wang
  -- strict thread matches above, loose matches on Subject: below --
2023-04-28  7:47 Zhenyu Wang
2023-02-23  8:50 Zhenyu Wang
2023-02-23 12:11 ` Jani Nikula
2021-04-29  8:51 Zhenyu Wang
2021-04-29 11:12 ` Jani Nikula
2021-04-21  9:45 Zhenyu Wang
2021-04-21 10:51 ` Jani Nikula
2021-02-22  8:34 Zhenyu Wang
2021-02-23 14:42 ` Rodrigo Vivi
2020-12-25  2:20 Zhenyu Wang
2021-01-05  7:54 ` Zhenyu Wang
2021-01-05  8:36   ` Jani Nikula
2021-01-05 20:44     ` Rodrigo Vivi
2020-08-05  8:02 Zhenyu Wang
2020-08-06 15:17 ` Jani Nikula
2020-05-28  3:35 Zhenyu Wang
2020-06-02 14:04 ` Joonas Lahtinen
2019-12-02  5:17 Zhenyu Wang
2019-12-02  5:17 ` [Intel-gfx] " Zhenyu Wang
2019-12-05  6:11 ` Zhenyu Wang
2019-12-05  8:14   ` Joonas Lahtinen
2019-12-05  8:49     ` Zhenyu Wang
2019-11-12  6:20 Zhenyu Wang
2019-11-12  6:20 ` [Intel-gfx] " Zhenyu Wang
2019-11-20 11:25 ` Joonas Lahtinen
2019-11-20 11:25   ` [Intel-gfx] " Joonas Lahtinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200403175033.GA3997092@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@intel.com \
    --cc=hang.yuan@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=yan.y.zhao@intel.com \
    --cc=zhenyuw@linux.intel.com \
    --cc=zhiyuan.lv@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).