From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: "Lahtinen, Joonas" <joonas.lahtinen@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/2] GVT-g guest patch for 4.8
Date: Tue, 06 Sep 2016 11:33:57 +0300 [thread overview]
Message-ID: <87y435xw96.fsf@intel.com> (raw)
In-Reply-To: <20160906064818.GG22557@nuc-i3427.alporthouse.com>
On Tue, 06 Sep 2016, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Tue, Sep 06, 2016 at 12:04:10PM +0800, Zhenyu Wang wrote:
>> Hi,
>>
>> Here're two patches for GVT-g guest to fix run against future GVT-g
>> host driver, which try to ensure 4.8 will be ready to use for VM.
>>
>> thanks.
>>
>> Ping Gao (1):
>> drm/i915: enable vGPU detection for all
>>
>> Zhi Wang (1):
>> drm/i915: disable 48bit full PPGTT when vGPU is active
>>
>> drivers/gpu/drm/i915/i915_gem_gtt.c | 9 ++++++---
>> drivers/gpu/drm/i915/i915_vgpu.c | 3 ---
>> 2 files changed, 6 insertions(+), 6 deletions(-)
>
> Acked-by: Chris Wilson <chris@chris-wilson.co.uk>
> -Chris
So these are needed for 4.8?
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-09-06 8:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 4:04 [PATCH 0/2] GVT-g guest patch for 4.8 Zhenyu Wang
2016-09-06 4:04 ` [PATCH 1/2] drm/i915: enable vGPU detection for all Zhenyu Wang
2016-09-06 7:51 ` Joonas Lahtinen
2016-09-06 4:04 ` [PATCH 2/2] drm/i915: disable 48bit full PPGTT when vGPU is active Zhenyu Wang
2016-09-06 7:55 ` Joonas Lahtinen
2016-09-06 4:56 ` ✗ Fi.CI.BAT: warning for GVT-g guest patch for 4.8 Patchwork
2016-09-06 6:48 ` [PATCH 0/2] " Chris Wilson
2016-09-06 8:33 ` Jani Nikula [this message]
2016-09-06 8:35 ` Zhenyu Wang
2016-09-06 13:43 ` Jani Nikula
2016-09-06 13:56 ` Jani Nikula
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=87y435xw96.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@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 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.