From: Colin Xu <colin.xu@intel.com>
To: intel-gvt-dev@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org, zhenyuw@linux.intel.com
Subject: [Intel-gfx] [PATCH v5 0/2] Enable GVT suspend/resume
Date: Fri, 16 Oct 2020 16:11:18 +0800 [thread overview]
Message-ID: <20201016081118.375301-1-colin.xu@intel.com> (raw)
This patchset enables GVT suspend/resume so that GVT enabled VM can
continue running after host resuming from suspend state.
V2:
- Change kzalloc/kfree to vzalloc/vfree since the space allocated
from kmalloc may not enough for all saved GGTT entries.
- Keep gvt suspend/resume wrapper in intel_gvt.h/intel_gvt.c and
move the actual implementation to gvt.h/gvt.c. (zhenyu)
- Check gvt config on and active with intel_gvt_active(). (zhenyu)
V3: (zhenyu)
- Incorrect copy length. Should be num entries * entry size.
- Use memcpy_toio()/memcpy_fromio() instead of memcpy for iomem.
- Add F_PM_SAVE flags to indicate which MMIOs to save/restore for PM.
V4:
Rebase.
V5:
Fail intel_gvt_pm_suspend if fail to save ggtt.
Colin Xu (2):
drm/i915/gvt: Save/restore HW status for GVT during suspend/resume
drm/i915/gvt: Add GVT suspend/resume routine to i915
drivers/gpu/drm/i915/gvt/gtt.c | 88 +++++++++++++++++++++++++++++
drivers/gpu/drm/i915/gvt/gtt.h | 2 +
drivers/gpu/drm/i915/gvt/gvt.c | 14 +++++
drivers/gpu/drm/i915/gvt/gvt.h | 7 +++
drivers/gpu/drm/i915/gvt/handlers.c | 39 ++++++++++++-
drivers/gpu/drm/i915/gvt/mmio.h | 3 +
drivers/gpu/drm/i915/gvt/vgpu.c | 1 +
drivers/gpu/drm/i915/i915_drv.c | 5 ++
drivers/gpu/drm/i915/intel_gvt.c | 30 ++++++++++
drivers/gpu/drm/i915/intel_gvt.h | 10 ++++
10 files changed, 196 insertions(+), 3 deletions(-)
--
2.28.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
reply other threads:[~2020-10-16 8:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201016081118.375301-1-colin.xu@intel.com \
--to=colin.xu@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--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