All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
	Jani Nikula <jani.nikula@intel.com>,
	Zhenyu Wang <zhenyuw@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] more gvt-next-fixes for 4.17
Date: Tue, 27 Mar 2018 16:42:28 +0300	[thread overview]
Message-ID: <152215814848.7428.17792518887701901268@jlahtine-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20180327083942.zahc6q2szcjkrqzn@zhen-hp.sh.intel.com>

Quoting Zhenyu Wang (2018-03-27 11:39:42)
> 
> Hi, Joonas
> 
> Here's this week's gvt-next-fixes queued for 4.17. One notable change
> is to revert previous workaround for gvt context preemption, now it
> has full support for preemption now. 

I've pulled the patches, but this revert sounds fishy. Is it something
that should have been done together with a commit in a batch introduced
to 4.17? To me, this sounds much like a feature patch, "enable
pre-emption on GVT context" is even written in the tag.

So I'm inclined to drop this patch from -fixes pull.

Is there some specific reason why you don't use Fixes: tagging to
make it easier to track which patches the fixes apply to, if there are
some?

Regards, Joonas

> Others are normal fixes and
> optimizations.
> 
> Thanks
> --
> The following changes since commit d8303075699292008ae5b2c8fc728d455b994c26:
> 
>   drm/i915/gvt: force to set all context control bits from guest (2018-03-19 17:33:30 +0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2018-03-27
> 
> for you to fetch changes up to 21e6e1af36a3c9b1c34bc441e5fa27cb36fbb830:
> 
>   drm/i915/gvt: Dereference msi eventfd_ctx when it isn't used anymore (2018-03-27 11:20:58 +0800)
> 
> ----------------------------------------------------------------
> gvt-next-fixes-2018-03-27
> 
> - fix unhandled vfio ioctl return value (Gerd)
> - revert gvt ctx preemption workaround, enable preemption
>   on gvt context! (Weinan)
> - no-op user interrupt for vGPU (Zhipeng)
> - fix eventfd ctx deference (Xiong)
> - misc cleanup
> 
> ----------------------------------------------------------------
> Gerd Hoffmann (1):
>       drm/i915/gvt: throw error on unhandled vfio ioctls
> 
> Gustavo A. R. Silva (1):
>       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"
> 
> Xiong Zhang (1):
>       drm/i915/gvt: Dereference msi eventfd_ctx when it isn't used anymore
> 
> Zhipeng Gong (1):
>       drm/i915/gvt: Make MI_USER_INTERRUPT nop in cmd parser
> 
>  drivers/gpu/drm/i915/gvt/cmd_parser.c |  1 +
>  drivers/gpu/drm/i915/gvt/handlers.c   |  1 +
>  drivers/gpu/drm/i915/gvt/kvmgt.c      | 18 ++++++++++++++++--
>  drivers/gpu/drm/i915/gvt/scheduler.c  |  3 ---
>  4 files changed, 18 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

  reply	other threads:[~2018-03-27 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-27  8:39 [PULL] more gvt-next-fixes for 4.17 Zhenyu Wang
2018-03-27 13:42 ` Joonas Lahtinen [this message]
2018-03-27 14:39   ` Joonas Lahtinen
2018-03-28  8:26     ` Zhenyu Wang
2018-03-30  6:36       ` Zhenyu Wang
2018-03-28  2:45   ` 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=152215814848.7428.17792518887701901268@jlahtine-desk.ger.corp.intel.com \
    --to=joonas.lahtinen@linux.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=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.