From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: "Nikula, Jani" <jani.nikula@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Yuan, Hang" <hang.yuan@intel.com>,
"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
"airlied@redhat.com" <airlied@redhat.com>,
"Vetter, Daniel" <daniel.vetter@intel.com>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [PULL] gvt-next-fixes
Date: Tue, 10 Sep 2019 10:36:57 +0800 [thread overview]
Message-ID: <20190910023657.GA12949@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <20190909223510.GA19671@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 4295 bytes --]
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-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev
--
Open Source Technology Center, Intel ltd.
$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-09-10 2:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 5:42 [PULL] gvt-next-fixes Zhenyu Wang
2019-09-06 16:58 ` Rodrigo Vivi
2019-09-09 17:24 ` Rodrigo Vivi
2019-09-09 21:54 ` Vetter, Daniel
2019-09-09 22:35 ` Rodrigo Vivi
2019-09-10 2:36 ` Zhenyu Wang [this message]
2019-09-10 21:24 ` Vetter, Daniel
-- strict thread matches above, loose matches on Subject: below --
2019-12-02 5:17 Zhenyu Wang
2019-11-12 6:20 Zhenyu Wang
2019-11-20 11:25 ` Joonas Lahtinen
2019-05-07 9:05 Zhenyu Wang
2019-05-07 12:44 ` Joonas Lahtinen
2018-08-14 7:31 Zhenyu Wang
2018-08-15 20:43 ` Rodrigo Vivi
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=20190910023657.GA12949@zhen-hp.sh.intel.com \
--to=zhenyuw@linux.intel.com \
--cc=airlied@redhat.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=rodrigo.vivi@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).