From: "Nilawar, Badal" <badal.nilawar@intel.com>
To: <janga.rahul.kumar@intel.com>, <igt-dev@lists.freedesktop.org>,
<ramadevi.gandi@intel.com>
Cc: <matthew.d.roper@intel.com>
Subject: Re: [PATCH i-g-t 1/2] tests/intel/xe_debugfs: Extend gt test to check mocs entry
Date: Thu, 2 May 2024 14:46:41 +0530 [thread overview]
Message-ID: <c5289376-1841-435b-a605-9ac4da26f521@intel.com> (raw)
In-Reply-To: <20240424200856.1194881-2-janga.rahul.kumar@intel.com>
On 25-04-2024 01:38, janga.rahul.kumar@intel.com wrote:
> From: Janga Rahul Kumar <janga.rahul.kumar@intel.com>
>
> Read and dump mocs debugfs entry.
>
> Cc: Matt Roper <matthew.d.roper@intel.com>
> Signed-off-by: Janga Rahul Kumar <janga.rahul.kumar@intel.com>
> ---
> tests/intel/xe_debugfs.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/tests/intel/xe_debugfs.c b/tests/intel/xe_debugfs.c
> index c5a586e9b..ba12f6ccc 100644
> --- a/tests/intel/xe_debugfs.c
> +++ b/tests/intel/xe_debugfs.c
> @@ -158,6 +158,7 @@ test_gt(int fd, int gt_id)
> "topology",
> "sa_info",
> "hw_engines",
> + "mocs",
> // "force_reset"
> };
> static const char * const expected_files_uc[] = {
> @@ -183,6 +184,10 @@ test_gt(int fd, int gt_id)
> igt_assert(igt_debugfs_exists(fd, name, O_RDONLY));
> igt_debugfs_dump(fd, name);
>
> + sprintf(name, "gt%d/mocs", gt_id);
> + igt_assert(igt_debugfs_exists(fd, name, O_RDONLY));
> + igt_debugfs_dump(fd, name);
Reviewed-by: Badal Nilawar <badal.nilawar@intel.com>
Regards,
Badal
> +
> sprintf(name, "gt%d/uc/guc_info", gt_id);
> igt_assert(igt_debugfs_exists(fd, name, O_RDONLY));
> igt_debugfs_dump(fd, name);
next prev parent reply other threads:[~2024-05-02 9:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 20:08 [PATCH i-g-t v2 0/2] Add mocs tests janga.rahul.kumar
2024-04-24 20:08 ` [PATCH i-g-t 1/2] tests/intel/xe_debugfs: Extend gt test to check mocs entry janga.rahul.kumar
2024-05-02 9:16 ` Nilawar, Badal [this message]
2024-04-24 20:08 ` [PATCH i-g-t v2 2/2] tests/intel/xe_pm: Add mocs suspend resume test janga.rahul.kumar
2024-05-02 9:02 ` Nilawar, Badal
2024-04-24 20:49 ` ✗ CI.xeBAT: failure for Add mocs tests (rev2) Patchwork
2024-04-24 20:51 ` ✗ Fi.CI.BAT: " Patchwork
2024-04-25 12:59 ` ✗ CI.xeFULL: " Patchwork
2024-04-30 12:51 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-30 17:47 ` ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-03-21 15:16 [PATCH i-g-t 0/2] Add mocs tests janga.rahul.kumar
2024-03-21 15:16 ` [PATCH i-g-t 1/2] tests/intel/xe_debugfs: Extend gt test to check mocs entry janga.rahul.kumar
2024-03-22 21:18 ` Matt Roper
2024-04-24 20:19 ` Kumar, Janga Rahul
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=c5289376-1841-435b-a605-9ac4da26f521@intel.com \
--to=badal.nilawar@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=janga.rahul.kumar@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=ramadevi.gandi@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