All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: joonas.lahtinen@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org, intel-gvt-dev@lists.freedesktop.org
Subject: [RFC PATCH v2 0/2] GVT device model split
Date: Mon, 26 Nov 2018 14:05:52 +0800	[thread overview]
Message-ID: <20181126060554.16481-1-zhenyuw@linux.intel.com> (raw)

Refresh previous attempt to split GVT module.

This trys to move GVT device model in stand alone module. New module
named as "i915_gvt" is created. The purpose is to enable GVT function
once user loads i915_gvt module.

This needs to export several i915 functions currently used by GVT as
in first patch. As GVT requires HW initial MMIO state for vGPU as base
initial state after create, which needs to be got from early stage of
i915 load, this trys to read all GVT tracked registers when i915 init,
and provide for i915_gvt module when host init.

I think we would refactor "kvmgt" module init first. "kvmgt" should
register into GVT as hypervisor interface provider, instead of making
GVT to load it for now. But that still won't split GVT from i915. So
this work takes further to split GVT device model from i915.

Thanks

Zhenyu Wang (2):
  drm/i915: Export current required functions for GVT
  drm/i915: Move GVT device model into separate module

 drivers/gpu/drm/i915/Kconfig              |    2 +-
 drivers/gpu/drm/i915/Makefile             |    4 +-
 drivers/gpu/drm/i915/gvt/Makefile         |    8 +-
 drivers/gpu/drm/i915/gvt/firmware.c       |    2 +-
 drivers/gpu/drm/i915/gvt/gvt.c            |   52 +-
 drivers/gpu/drm/i915/gvt/gvt.h            |    3 +
 drivers/gpu/drm/i915/i915_drv.c           |   43 +-
 drivers/gpu/drm/i915/i915_drv.h           |   10 +-
 drivers/gpu/drm/i915/i915_gem.c           |   11 +
 drivers/gpu/drm/i915/i915_gem_context.c   |    2 +
 drivers/gpu/drm/i915/i915_gem_dmabuf.c    |    1 +
 drivers/gpu/drm/i915/i915_gem_fence_reg.c |    2 +
 drivers/gpu/drm/i915/i915_gem_gtt.c       |    1 +
 drivers/gpu/drm/i915/i915_params.c        |    5 -
 drivers/gpu/drm/i915/i915_params.h        |    3 +-
 drivers/gpu/drm/i915/i915_request.c       |    3 +
 drivers/gpu/drm/i915/i915_vma.c           |    2 +
 drivers/gpu/drm/i915/intel_gvt.c          | 1519 ++++++++++++++++++++-
 drivers/gpu/drm/i915/intel_gvt.h          |   29 +-
 drivers/gpu/drm/i915/intel_ringbuffer.c   |    1 +
 drivers/gpu/drm/i915/intel_runtime_pm.c   |    2 +
 drivers/gpu/drm/i915/intel_uncore.c       |    3 +
 22 files changed, 1575 insertions(+), 133 deletions(-)

-- 
2.19.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2018-11-26  6:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26  6:05 Zhenyu Wang [this message]
2018-11-26  6:05 ` [RFC PATCH v2 1/2] drm/i915: Export current required functions for GVT Zhenyu Wang
2018-12-20  9:56   ` Joonas Lahtinen
2018-11-26  6:05 ` [RFC PATCH v2 2/2] drm/i915: Move GVT device model into separate module Zhenyu Wang
2018-12-20  9:58   ` Joonas Lahtinen
2018-11-26  6:23 ` ✗ Fi.CI.BAT: failure for GVT device model split Patchwork

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=20181126060554.16481-1-zhenyuw@linux.intel.com \
    --to=zhenyuw@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=joonas.lahtinen@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 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.