From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Weinan Li <weinan.z.li@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/3] mmio save restore refine in vgpu switch
Date: Mon, 11 Dec 2017 12:56:34 +0200 [thread overview]
Message-ID: <1512989794.5315.43.camel@linux.intel.com> (raw)
In-Reply-To: <1512621279-27199-1-git-send-email-weinan.z.li@intel.com>
Seems like you intended to send to gvt mailing list?
Regards, Joonas
On Thu, 2017-12-07 at 12:34 +0800, Weinan Li wrote:
> Merge switch_mmio_to_vgpu and switch_mmio_to_host, use delta update for
> mocs save restore, deal host mocs value as fixed, it won't be changed after
> initialization. These can save vgpu switch time to reduce CPU utilization
> and improve GPU performance in GVT-g with multi-VMs.
>
> Weinan Li (3):
> drm/i915/gvt: optimize for vGPU mmio switch
> drm/i915/gvt: refine mocs save restore policy
> drm/i915/gvt: load host render mocs once in mocs switch
>
> drivers/gpu/drm/i915/gvt/cmd_parser.c | 19 +++
> drivers/gpu/drm/i915/gvt/render.c | 252 +++++++++++++++++-----------------
> drivers/gpu/drm/i915/gvt/trace.h | 15 +-
> 3 files changed, 152 insertions(+), 134 deletions(-)
>
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-12-11 10:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 4:34 [PATCH 0/3] mmio save restore refine in vgpu switch Weinan Li
2017-12-07 4:34 ` [PATCH 1/3] drm/i915/gvt: optimize for vGPU mmio switch Weinan Li
2017-12-07 4:34 ` [PATCH 2/3] drm/i915/gvt: refine mocs save restore policy Weinan Li
2017-12-07 4:34 ` [PATCH 3/3] drm/i915/gvt: load host render mocs once in mocs switch Weinan Li
2017-12-07 4:49 ` ✗ Fi.CI.BAT: failure for mmio save restore refine in vgpu switch Patchwork
2017-12-11 10:56 ` Joonas Lahtinen [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=1512989794.5315.43.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=weinan.z.li@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.