From: "Du, Changbin" <changbin.du@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org, intel-gvt-dev@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Add interface to reserve fence registers for vGPU
Date: Thu, 31 Aug 2017 11:21:02 +0800 [thread overview]
Message-ID: <20170831032101.GA7935@intel.com> (raw)
In-Reply-To: <150408523885.916.14973316317495497931@mail.alporthouse.com>
[-- Attachment #1.1: Type: text/plain, Size: 978 bytes --]
Hi chris,
On Wed, Aug 30, 2017 at 10:27:18AM +0100, Chris Wilson wrote:
> Quoting changbin.du@intel.com (2017-08-30 09:54:21)
> > This patch added two new api to the fence management code:
> > - i915_reserve_one_fence() will try to find a free fence from fence_list
> > and force-remove vma if need.
> > - i915_giveback_reserved_fence() reclaim a reserved fence after vGPU has
> > finished.
>
> Symmetry: reserve_fence, unreserve_fence.
>
ok, I will rename the functions.
> We need a safeguard here so that the host is able to always able allocate
> to allocate a fence for the display engine. (That requirement should be
> quite soft for modern hw, nevertheless it should be in the design to
> prevent overuse from leading to an unusable system.)
> -Chris
Yes, agree. Is there any other components always need a fence ready? otherwise,
I will add a safeguard to ensure at least 1 fence register remained for host.
--
Thanks,
Changbin Du
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 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:[~2017-08-31 3:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 8:54 [PATCH] drm/i915: Add interface to reserve fence registers for vGPU changbin.du
2017-08-30 9:19 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-08-30 9:27 ` [PATCH] " Chris Wilson
2017-08-31 3:21 ` Du, Changbin [this message]
2017-08-30 10:34 ` ✗ Fi.CI.IGT: failure for " Patchwork
2017-09-01 7:08 ` [PATCH v2] " changbin.du
2017-09-01 10:59 ` Chris Wilson
2017-09-04 6:08 ` Du, Changbin
2017-09-01 7:38 ` ✓ Fi.CI.BAT: success for drm/i915: Add interface to reserve fence registers for vGPU (rev2) Patchwork
2017-09-01 8:42 ` ✗ Fi.CI.IGT: warning " 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=20170831032101.GA7935@intel.com \
--to=changbin.du@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@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 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.