All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>,
	"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
	"Yuan, Hang" <hang.yuan@intel.com>
Subject: Re: [PULL] gvt-fixes
Date: Thu, 31 Jan 2019 11:45:33 +0200	[thread overview]
Message-ID: <87ftt9yxc2.fsf@intel.com> (raw)
In-Reply-To: <20190124054801.GP7203@zhen-hp.sh.intel.com>

On Thu, 24 Jan 2019, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> Hi,
>
> Here's one fix for gvt to destroy shadow batch and indirect context
> properly.

I seem to have failed to let you know that I've pulled this.

Thanks,
Jani.



>
> Thanks.
> --
> The following changes since commit 51b00d8509dc69c98740da2ad07308b630d3eb7d:
>
>   drm/i915/gvt: Fix mmap range check (2019-01-15 19:04:45 +0800)
>
> are available in the Git repository at:
>
>   https://github.com/intel/gvt-linux.git tags/gvt-fixes-2019-01-24
>
> for you to fetch changes up to 0f75551216091223efe1f18295f655aff6415385:
>
>   drm/i915/gvt: release shadow batch buffer and wa_ctx before destroy one workload (2019-01-23 13:58:46 +0800)
>
> ----------------------------------------------------------------
> gvt-fixes-2019-01-24
>
> - Fix destroy of shadow batch and indirect ctx (Weinan)
>
> ----------------------------------------------------------------
> Weinan Li (1):
>       drm/i915/gvt: release shadow batch buffer and wa_ctx before destroy one workload
>
>  drivers/gpu/drm/i915/gvt/scheduler.c | 11 ++++++-----
>  1 file changed, 6 insertions(+), 5 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

  reply	other threads:[~2019-01-31  9:45 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24  5:48 [PULL] gvt-fixes Zhenyu Wang
2019-01-31  9:45 ` Jani Nikula [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-03-21  3:50 Zhenyu Wang
2019-03-21 20:03 ` Rodrigo Vivi
2019-04-02  9:40 Zhenyu Wang
2019-04-04  0:12 ` Rodrigo Vivi
2019-04-04  0:32   ` Zhenyu Wang
2019-04-04  1:03     ` Rodrigo Vivi
2019-04-04  0:39   ` Zhenyu Wang
2019-04-11  6:49 Zhenyu Wang
2019-04-11 16:48 ` Rodrigo Vivi
2019-05-21  6:24 Zhenyu Wang
2019-05-21 12:35 ` Joonas Lahtinen
2019-05-29  9:06 Zhenyu Wang
2019-05-29 12:07 ` Joonas Lahtinen
2019-05-30  3:41   ` Zhenyu Wang
2019-05-31  8:16     ` Joonas Lahtinen
2019-06-05  8:49 Zhenyu Wang
2019-06-06 12:04 ` Joonas Lahtinen
2019-06-19  6:22 Zhenyu Wang
2019-06-19  7:56 ` Jani Nikula
2019-07-23  9:29 Zhenyu Wang
2019-07-29  3:33 ` Zhenyu Wang
2019-07-29 11:05   ` Jani Nikula
2019-07-30  7:00     ` Zhenyu Wang
2019-07-30  8:33       ` Jani Nikula
2019-08-13  9:58 Zhenyu Wang
2019-08-13 13:41 ` Jani Nikula
2019-11-12  6:18 Zhenyu Wang
2019-11-12 20:36 ` Vivi, Rodrigo
2019-11-22  3:33 Zhenyu Wang
2024-01-31  9:38 Zhenyu Wang
2024-02-01 14:44 ` Joonas Lahtinen
2024-02-05  3:21   ` Zhenyu Wang

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=87ftt9yxc2.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=hang.yuan@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=rodrigo.vivi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.