From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Weinan Li <weinan.z.li@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v6] drm/i915: enable to read CSB and CSB write pointer from HWSP in GVT-g VM
Date: Mon, 16 Oct 2017 14:00:26 +0300 [thread overview]
Message-ID: <1508151626.5300.30.camel@linux.intel.com> (raw)
In-Reply-To: <150805816884.3226.16587999096567934889@mail.alporthouse.com>
On Sun, 2017-10-15 at 10:02 +0100, Chris Wilson wrote:
> Quoting Weinan Li (2017-10-15 04:55:25)
> > Let GVT-g VM read the CSB and CSB write pointer from virtual HWSP, not all
> > the host support this feature, need to check the BIT(3) of caps in PVINFO.
> >
> > v3 : Remove unnecessary comments.
> > v4 : Separate VM enable patch with GVT-g implementation patch due to code
> > dependency.
> > v5 : Use inline for GVT virtual HWSP caps check function.
> > v6 : Comments refine.
> >
> > Signed-off-by: Weinan Li <weinan.z.li@intel.com>
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Pushed the patch, thanks for supplying and reviewing it.
Regards, Joonas
--
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-10-16 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 3:55 [PATCH v6] drm/i915: enable to read CSB and CSB write pointer from HWSP in GVT-g VM Weinan Li
2017-10-15 4:22 ` ✗ Fi.CI.BAT: failure for drm/i915: enable to read CSB and CSB write pointer from HWSP in GVT-g VM (rev3) Patchwork
2017-10-15 9:02 ` [PATCH v6] drm/i915: enable to read CSB and CSB write pointer from HWSP in GVT-g VM Chris Wilson
2017-10-16 11:00 ` 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=1508151626.5300.30.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox