From: Jani Nikula <jani.nikula@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [GIT PULL] gvt-next pull
Date: Thu, 21 Sep 2017 16:18:00 +0300 [thread overview]
Message-ID: <87mv5o5gxj.fsf@nikula.org> (raw)
In-Reply-To: <20170908063155.l54lvpivxntjm7hq@zhen-hp.sh.intel.com>
On Fri, 08 Sep 2017, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> Hi,
>
> This is an earlier request for gvt-next pull which is mainly
> for required PCI config changes on OVMF support for Redhat and
> also contains massive error handling improvement on workload
> submission. Both are targeted for 4.15.
N.b. I've pulled this ages ago, just forgot to reply on the list.
BR,
Jani.
>
> Thanks
> --
> The following changes since commit bb9d2d050503c69695557b8b741276686ca2a396:
>
> drm/i915: Update DRIVER_DATE to 20170907 (2017-09-07 11:28:20 +0300)
>
> are available in the git repository at:
>
> https://github.com/01org/gvt-linux.git tags/gvt-next-2017-09-08
>
> for you to fetch changes up to 02d578e5edd980eac3fbed15db4d9e5665f22089:
>
> drm/i915/gvt: Add support for PCIe extended configuration space (2017-09-08 14:21:16 +0800)
>
> ----------------------------------------------------------------
> gvt-next-2017-09-08
>
> - PCI config sanitize series (Changbin)
> - Workload submission error handling series (Fred)
>
> ----------------------------------------------------------------
> Changbin Du (4):
> drm/i915/kvmgt: Sanitize PCI bar emulation
> drm/i915/gvt: Add emulation for BAR2 (aperture) with normal file RW approach
> drm/i915/gvt: Fix incorrect PCI BARs reporting
> drm/i915/gvt: Add support for PCIe extended configuration space
>
> fred gao (6):
> drm/i915/gvt: Separate cmd scan from request allocation
> drm/i915/gvt: Add error handling for intel_gvt_scan_and_shadow_workload
> drm/i915/gvt: Refine error handling for prepare_execlist_workload
> drm/i915/gvt: Refine error handling for intel_vgpu_pin_mm
> drm/i915/gvt: Refine error handling in dispatch_workload
> drm/i915/gvt: Refine error handling for perform_bb_shadow
>
> drivers/gpu/drm/i915/gvt/cfg_space.c | 143 +++++++++++++++++-----------------
> drivers/gpu/drm/i915/gvt/cmd_parser.c | 37 +++++----
> drivers/gpu/drm/i915/gvt/execlist.c | 127 ++++++++++++++++++++++--------
> drivers/gpu/drm/i915/gvt/gtt.c | 3 +-
> drivers/gpu/drm/i915/gvt/gvt.c | 2 +-
> drivers/gpu/drm/i915/gvt/gvt.h | 14 +++-
> drivers/gpu/drm/i915/gvt/kvmgt.c | 44 ++++++-----
> drivers/gpu/drm/i915/gvt/mmio.c | 47 ++++++++++-
> drivers/gpu/drm/i915/gvt/scheduler.c | 110 ++++++++++++++++++--------
> drivers/gpu/drm/i915/gvt/scheduler.h | 1 +
> 10 files changed, 353 insertions(+), 175 deletions(-)
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-09-21 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 6:31 [GIT PULL] gvt-next pull Zhenyu Wang
2017-09-21 13:18 ` Jani Nikula [this message]
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=87mv5o5gxj.fsf@nikula.org \
--to=jani.nikula@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 \
/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