From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 03/15] drm/i915: add I915_BO_ALLOC_GPU_ONLY
Date: Fri, 11 Feb 2022 10:23:33 +0100 [thread overview]
Message-ID: <3e964cee-df79-1349-787a-9ddeba75c85a@linux.intel.com> (raw)
In-Reply-To: <20220210121313.701004-4-matthew.auld@intel.com>
On 2/10/22 13:13, Matthew Auld wrote:
> If the user doesn't require CPU access for the buffer, then
> ALLOC_GPU_ONLY should be used, in order to prioritise allocating in the
> non-mappable portion of LMEM, on devices with small BAR.
>
> v2(Thomas):
> - The BO_ALLOC_TOPDOWN naming here is poor, since this is pure lies on
> systems that don't even have small BAR. A better name is GPU_ONLY,
> which is accurate regardless of the configuration.
>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
next prev parent reply other threads:[~2022-02-11 9:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 12:12 [PATCH v2 00/15] Initial support for small BAR recovery Matthew Auld
2022-02-10 12:12 ` [PATCH v2 01/15] drm/i915: add io_size plumbing Matthew Auld
2022-02-10 12:13 ` [PATCH v2 02/15] drm/i915/ttm: require mappable by default Matthew Auld
2022-02-11 9:20 ` Thomas Hellström
2022-02-10 12:13 ` [PATCH v2 03/15] drm/i915: add I915_BO_ALLOC_GPU_ONLY Matthew Auld
2022-02-11 9:23 ` Thomas Hellström [this message]
2022-02-10 12:13 ` [PATCH v2 04/15] drm/i915/buddy: track available visible size Matthew Auld
2022-02-11 9:25 ` Thomas Hellström
2022-02-10 12:13 ` [PATCH v2 05/15] drm/i915/buddy: adjust res->start Matthew Auld
2022-02-10 12:13 ` [PATCH v2 06/15] drm/i915/buddy: tweak 2big check Matthew Auld
2022-02-10 12:13 ` [PATCH v2 07/15] drm/i915/selftests: mock test io_size Matthew Auld
2022-02-10 12:13 ` [PATCH v2 08/15] drm/i915/ttm: make eviction mappable aware Matthew Auld
2022-02-10 12:13 ` [PATCH v2 09/15] drm/i915/ttm: mappable migration on fault Matthew Auld
2022-02-10 12:13 ` [PATCH v2 10/15] drm/i915/selftests: exercise mmap migration Matthew Auld
2022-02-11 9:36 ` Thomas Hellström
2022-02-10 12:13 ` [PATCH v2 11/15] drm/i915/selftests: handle allocation failures Matthew Auld
2022-02-11 9:37 ` Thomas Hellström
2022-02-10 12:13 ` [PATCH v2 12/15] drm/i915/create: apply ALLOC_GPU_ONLY by default Matthew Auld
2022-02-11 9:49 ` Thomas Hellström
2022-02-11 9:52 ` [Intel-gfx] " Matthew Auld
2022-02-11 9:55 ` Thomas Hellström
2022-02-11 10:00 ` Matthew Auld
2022-02-11 10:14 ` Thomas Hellström
2022-02-10 12:13 ` [PATCH v2 13/15] drm/i915/uapi: add NEEDS_CPU_ACCESS hint Matthew Auld
2022-02-11 9:59 ` Thomas Hellström
2022-02-10 12:13 ` [PATCH v2 14/15] drm/i915/uapi: forbid ALLOC_GPU_ONLY for error capture Matthew Auld
2022-02-11 10:06 ` Thomas Hellström
2022-02-10 12:13 ` [PATCH v2 15/15] drm/i915/lmem: don't treat small BAR as an error Matthew Auld
2022-02-11 10:08 ` Thomas Hellström
2022-02-10 14:40 ` [Intel-gfx] [PATCH v2 00/15] Initial support for small BAR recovery Das, Nirmoy
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=3e964cee-df79-1349-787a-9ddeba75c85a@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@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