From: Mohammed Thasleem <mohammed.thasleem@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [PATCH v3 0/2] Cache xe_device info for lease fd
Date: Tue, 2 Jan 2024 13:39:21 +0530 [thread overview]
Message-ID: <20240102080923.97366-1-mohammed.thasleem@intel.com> (raw)
In case of xe device for lessor fd, the xe_device struct gets
created and cached during drm_open. But for the lessee fd,
the xe_device info struct is not created and cached.
Mohammed Thasleem (2):
HAX/DO_NOT_MERGE: Patch adding to test to kms_lease
tests/kms_lease: Cache xe_device info for lease fd
tests/intel-ci/xe-fast-feedback.testlist | 283 ++---------------------
tests/kms_lease.c | 10 +
2 files changed, 31 insertions(+), 262 deletions(-)
--
2.25.1
next reply other threads:[~2024-01-02 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 8:09 Mohammed Thasleem [this message]
2024-01-02 8:09 ` [PATCH v3 1/2] HAX/DO_NOT_MERGE: Patch adding to test to kms_lease Mohammed Thasleem
2024-01-02 18:35 ` [PATCH v1 2/2] " Mohammed Thasleem
2024-01-02 8:09 ` [PATCH v3 2/2] tests/kms_lease: Cache xe_device info for lease fd Mohammed Thasleem
-- strict thread matches above, loose matches on Subject: below --
2022-04-22 2:04 [PATCH v3 0/2] " Mohammed Thasleem
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=20240102080923.97366-1-mohammed.thasleem@intel.com \
--to=mohammed.thasleem@intel.com \
--cc=igt-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox