From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: "Wang, Zhi A" <zhi.a.wang@intel.com>
Cc: "Auld, Matthew" <matthew.auld@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v4] drm/i915: Remove i915.enable_ppgtt override
Date: Tue, 9 Oct 2018 10:15:07 +0800 [thread overview]
Message-ID: <20181009021507.GB14570@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <F3B0350DF4CB6849A642218320DE483D7D888DB0@SHSMSX104.ccr.corp.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 832 bytes --]
On 2018.10.08 13:58:25 +0000, Wang, Zhi A wrote:
> Thanks for pointing this. My bad.
>
> I take a look on the code and it looks like the GVT-g context is now quite similar with the kernel context except the force single submission and ring buffer size. (When we upstream the code, there was no kernel context at that time. :/) Now there is already one API for single submission. If we can introduce another one to configure the ring buffer size. Then maybe we can remove the *create_gvt() in i915_gem_context.c and used kernel context instead.
>
> Feel free to drop comments. :)
>
For ppgtt, you'd better change to use i915 ppgtt interface to handle
shadow pages, then gvt context would be much like normal one.
--
Open Source Technology Center, Intel ltd.
$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-10-09 2:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 11:48 [PATCH v4] drm/i915: Remove i915.enable_ppgtt override Chris Wilson
2018-09-25 12:06 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2018-09-25 12:28 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-09-25 13:14 ` Patchwork
2018-09-25 13:22 ` [PATCH v4] " Joonas Lahtinen
2018-09-25 18:01 ` Zhi Wang
2018-09-26 1:06 ` He, Min
2018-09-26 8:02 ` Joonas Lahtinen
2018-09-26 12:29 ` Zhi Wang
2018-10-08 9:53 ` Zhenyu Wang
2018-10-08 13:58 ` Wang, Zhi A
2018-10-09 2:15 ` Zhenyu Wang [this message]
2018-10-09 6:55 ` Zhi Wang
2018-10-09 7:35 ` Chris Wilson
2018-09-25 13:27 ` Joonas Lahtinen
2018-09-26 13:16 ` Joonas Lahtinen
2018-09-26 20:12 ` [PATCH v5] " Chris Wilson
2018-09-27 8:20 ` Joonas Lahtinen
2018-09-27 8:55 ` Chris Wilson
2018-09-27 10:57 ` Joonas Lahtinen
2018-09-27 11:07 ` Chris Wilson
2018-09-26 21:34 ` ✗ Fi.CI.SPARSE: warning for drm/i915: Remove i915.enable_ppgtt override (rev2) Patchwork
2018-09-26 21:55 ` ✓ Fi.CI.BAT: success " Patchwork
2018-09-27 3:00 ` ✓ Fi.CI.IGT: " 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=20181009021507.GB14570@zhen-hp.sh.intel.com \
--to=zhenyuw@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=zhi.a.wang@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.