From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
igt-dev@lists.freedesktop.org, Nirmoy Das <nirmoy.das@intel.com>,
andi.shyti@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t 1/3] lib/igt_gt: Add a method to detect ggtt bind
Date: Thu, 14 Sep 2023 21:13:47 +0200 [thread overview]
Message-ID: <d475d800-603e-1df8-f3cb-ff5c53fcd972@linux.intel.com> (raw)
In-Reply-To: <20230914133151.6rpyuaeamby4bkf4@kamilkon-desk.igk.intel.com>
Hi Kamil,
On 9/14/2023 3:31 PM, Kamil Konieczny wrote:
> Hi Nirmoy,
>
> On 2023-09-13 at 11:42:50 +0200, Nirmoy Das wrote:
>> On MTL GGTT updates happens through MI_UPDATE_GGTT command.
>> Add a method to detect that.
>>
>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
>> ---
>> lib/igt_gt.c | 5 +++++
>> lib/igt_gt.h | 1 +
>> 2 files changed, 6 insertions(+)
>>
>> diff --git a/lib/igt_gt.c b/lib/igt_gt.c
>> index a24a566c7..6895964a9 100644
>> --- a/lib/igt_gt.c
>> +++ b/lib/igt_gt.c
>> @@ -659,3 +659,8 @@ int gem_execbuf_flags_to_engine_class(unsigned int flags)
>> igt_assert(0);
>> }
>> }
>> +
> Add description to public function.
Makes sense, will resend with doc.
Nirmoy
>
> Regards,
> Kamil
>
>> +bool gem_has_ggtt_bind(int fd)
>> +{
>> + return IS_METEORLAKE(intel_get_drm_devid(fd));
>> +}
>> diff --git a/lib/igt_gt.h b/lib/igt_gt.h
>> index 3d10349e4..7d35a209d 100644
>> --- a/lib/igt_gt.h
>> +++ b/lib/igt_gt.h
>> @@ -83,5 +83,6 @@ extern const struct intel_execution_engine2 {
>> } intel_execution_engines2[];
>>
>> int gem_execbuf_flags_to_engine_class(unsigned int flags);
>> +bool gem_has_ggtt_bind(int fd);
>>
>> #endif /* IGT_GT_H */
>> --
>> 2.41.0
>>
next prev parent reply other threads:[~2023-09-14 19:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 9:42 [igt-dev] [PATCH i-g-t 0/3] Ignore some tests on MTL which Nirmoy Das
2023-09-13 9:42 ` [igt-dev] [PATCH i-g-t 1/3] lib/igt_gt: Add a method to detect ggtt bind Nirmoy Das
2023-09-14 13:31 ` Kamil Konieczny
2023-09-14 19:13 ` Nirmoy Das [this message]
2023-09-13 9:42 ` [igt-dev] [PATCH i-g-t 2/3] tests/intel/gem_ctx_shared: Skip some test on MTL Nirmoy Das
2023-09-14 13:50 ` Kamil Konieczny
2023-09-14 19:13 ` Nirmoy Das
2023-09-13 9:42 ` [igt-dev] [PATCH i-g-t 3/3] tests/intel/gem_ctx_schedule: " Nirmoy Das
2023-09-13 10:54 ` [igt-dev] ✗ Fi.CI.BAT: failure for Ignore some tests on MTL which (rev2) Patchwork
2023-09-13 11:51 ` [igt-dev] ✓ CI.xeBAT: success " 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=d475d800-603e-1df8-f3cb-ff5c53fcd972@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=andi.shyti@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=nirmoy.das@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