From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/4] drm/i915: Remove i915_gem_context_create_gvt()
Date: Mon, 12 Aug 2019 15:57:56 +0800 [thread overview]
Message-ID: <20190812075756.GD14790@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <156536737864.32306.8520357726207994926@skylake-alporthouse-com>
[-- Attachment #1.1: Type: text/plain, Size: 1260 bytes --]
On 2019.08.09 17:16:18 +0100, Chris Wilson wrote:
> Quoting Mika Kuoppala (2019-08-09 17:12:20)
> > Chris Wilson <chris@chris-wilson.co.uk> writes:
> >
> > > As we are phasing out using the GEM context for internal clients that
> > > need to manipulate logical context state directly, remove the
> > > constructor for the GVT context. We are not using it for anything other
> > > than default setup and allocation of an i915_ppgtt.
> > >
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> >
> > Not familiar with gvt but seems to create similar enough
> > context.
> >
> > Higher priority, not closed and using more strict
> > lock.
>
> I thought they would appreciate the higher priority ;)
>
> gvt currently doesn't have anyway for it to determine the relative
> priority of its guest vs the host, so if we set it too low we impact the
> qos of the guest, too high and its affects the qos of the host. Keeping
> it at max user though still gives the kernel some leeway to usurp it.
> And who knows one day we may get a scheduler.
yep, appreciate that. ;)
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
--
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: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-08-12 8:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 15:41 [PATCH 1/4] drm/i915: Remove i915_gem_context_create_gvt() Chris Wilson
2019-08-09 15:41 ` [PATCH 2/4] drm/i915/gt: Make deferred context allocation explicit Chris Wilson
2019-08-09 16:56 ` [PATCH] " Chris Wilson
2019-08-09 15:41 ` [PATCH 3/4] drm/i915: Push the ring creation flags to the backend Chris Wilson
2019-08-09 15:41 ` [PATCH 4/4] drm/i915: Lift timeline into intel_context Chris Wilson
2019-08-09 16:12 ` [PATCH 1/4] drm/i915: Remove i915_gem_context_create_gvt() Mika Kuoppala
2019-08-09 16:16 ` Chris Wilson
2019-08-12 7:57 ` Zhenyu Wang [this message]
2019-08-09 18:06 ` ✓ Fi.CI.BAT: success for series starting with [1/4] drm/i915: Remove i915_gem_context_create_gvt() (rev2) Patchwork
2019-08-10 13:52 ` ✓ 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=20190812075756.GD14790@zhen-hp.sh.intel.com \
--to=zhenyuw@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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