From: Jani Nikula <jani.nikula@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: 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
Date: Tue, 24 Nov 2020 11:48:11 +0200 [thread overview]
Message-ID: <87k0ubm6g4.fsf@intel.com> (raw)
In-Reply-To: <20201124031359.GE16939@zhen-hp.sh.intel.com>
On Tue, 24 Nov 2020, Zhenyu Wang <zhenyuw@linux.intel.com> 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-dev@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
next prev parent reply other threads:[~2020-11-24 9:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 9:05 [Intel-gfx] [PULL] gvt-next Zhenyu Wang
2020-11-23 9:32 ` Joonas Lahtinen
2020-11-24 3:13 ` Zhenyu Wang
2020-11-24 9:48 ` Jani Nikula [this message]
2020-11-27 13:26 ` Joonas Lahtinen
-- strict thread matches above, loose matches on Subject: below --
2022-11-11 8:59 Zhenyu Wang
2022-11-15 15:36 ` Rodrigo Vivi
2022-11-17 3:02 ` Zhenyu Wang
2022-11-17 3:37 ` Vivi, Rodrigo
2022-11-17 5:28 ` Zhenyu Wang
2022-11-17 6:41 ` Zhenyu Wang
2022-11-17 13:49 ` Rodrigo Vivi
2022-04-26 7:58 Wang, Zhi A
2022-04-26 8:37 ` Jani Nikula
2022-04-26 8:38 ` Wang, Zhi A
2022-04-26 8:42 ` Wang, Zhi A
2022-04-26 11:52 ` Jason Gunthorpe
2022-04-28 21:35 ` Alex Williamson
2022-04-28 21:48 ` Alex Williamson
2022-04-26 15:53 ` Jason Gunthorpe
2022-04-26 16:58 ` Wang, Zhi A
2022-04-26 19:19 ` Robert Beckett
2022-04-20 8:04 Wang, Zhi A
2022-04-20 12:13 ` Jason Gunthorpe
2022-04-20 14:41 ` Wang, Zhi A
2022-04-20 15:02 ` Jason Gunthorpe
2022-04-20 16:13 ` Wang, Zhi A
2021-03-16 7:43 Zhenyu Wang
2021-03-16 11:52 ` Jani Nikula
2020-09-10 5:37 Zhenyu Wang
2020-09-11 23:58 ` Rodrigo Vivi
2020-09-14 2:34 ` Zhenyu Wang
2020-09-14 18:39 ` Vivi, Rodrigo
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=87k0ubm6g4.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=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