From: Matthew Auld <matthew.auld@intel.com>
To: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>,
igt-dev@lists.freedesktop.org
Cc: tvrtko.ursulin@intel.com, thomas.hellstrom@intel.com,
daniel.vetter@intel.com, petri.latvala@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t v6 01/13] lib/i915: memory region gtt_alignment support
Date: Wed, 9 Nov 2022 12:40:08 +0000 [thread overview]
Message-ID: <0aa82aea-cabe-0ea5-ea0c-809d619c335e@intel.com> (raw)
In-Reply-To: <20221107085256.17293-2-niranjana.vishwanathapura@intel.com>
On 07/11/2022 08:52, Niranjana Vishwanathapura wrote:
> Update library to include gtt_alignment field to support
> platforms with 64K device memory pages.
>
> v2: Do not pull in gtt_alignment uapi
>
> Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
next prev parent reply other threads:[~2022-11-09 12:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 8:52 [igt-dev] [PATCH i-g-t v6 00/13] vm_bind: Add VM_BIND validation support Niranjana Vishwanathapura
2022-11-07 8:52 ` [igt-dev] [PATCH i-g-t v6 01/13] lib/i915: memory region gtt_alignment support Niranjana Vishwanathapura
2022-11-09 12:40 ` Matthew Auld [this message]
2022-11-07 8:52 ` [igt-dev] [PATCH i-g-t v6 02/13] lib/vm_bind: import uapi definitions Niranjana Vishwanathapura
2022-11-07 8:52 ` [igt-dev] [PATCH i-g-t v6 03/13] lib/vm_bind: Add vm_bind/unbind and execbuf3 ioctls Niranjana Vishwanathapura
2022-11-07 8:52 ` [igt-dev] [PATCH i-g-t v6 04/13] lib/vm_bind: Add vm_bind mode support for VM Niranjana Vishwanathapura
2022-11-07 8:52 ` [igt-dev] [PATCH i-g-t v6 05/13] lib/vm_bind: Add vm_bind specific library functions Niranjana Vishwanathapura
2022-11-07 8:52 ` [igt-dev] [PATCH i-g-t v6 06/13] lib/vm_bind: Add __prime_handle_to_fd() Niranjana Vishwanathapura
2022-11-07 8:52 ` [igt-dev] [PATCH i-g-t v6 07/13] tests/i915/vm_bind: Add vm_bind sanity test Niranjana Vishwanathapura
2022-11-07 8:52 ` [igt-dev] [PATCH i-g-t v6 08/13] tests/i915/vm_bind: Add basic VM_BIND test support Niranjana Vishwanathapura
2022-11-07 8:52 ` [igt-dev] [PATCH i-g-t v6 09/13] tests/i915/vm_bind: Add userptr subtest Niranjana Vishwanathapura
2022-11-07 8:52 ` [igt-dev] [PATCH i-g-t v6 10/13] tests/i915/vm_bind: Add gem_exec3_basic test Niranjana Vishwanathapura
2022-11-07 8:52 ` [igt-dev] [PATCH i-g-t v6 11/13] tests/i915/vm_bind: Add gem_exec3_balancer test Niranjana Vishwanathapura
2022-11-07 8:52 ` [igt-dev] [PATCH i-g-t v6 12/13] tests/i915/vm_bind: Add gem_lmem_swapping@vm_bind sub test Niranjana Vishwanathapura
2022-11-07 8:52 ` [igt-dev] [PATCH i-g-t v6 13/13] tests/i915/vm_bind: Add gem_shrink@vm_bind* subtests Niranjana Vishwanathapura
2022-11-09 12:38 ` Matthew Auld
2022-11-09 16:02 ` Niranjana Vishwanathapura
2022-11-07 11:02 ` [igt-dev] ✗ GitLab.Pipeline: warning for vm_bind: Add VM_BIND validation support (rev10) Patchwork
2022-11-07 11:18 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2022-11-07 13:33 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=0aa82aea-cabe-0ea5-ea0c-809d619c335e@intel.com \
--to=matthew.auld@intel.com \
--cc=daniel.vetter@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=niranjana.vishwanathapura@intel.com \
--cc=petri.latvala@intel.com \
--cc=thomas.hellstrom@intel.com \
--cc=tvrtko.ursulin@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