From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 2/2] tests/intel/xe_oa: Tests for OA syncs
Date: Fri, 25 Oct 2024 12:45:51 -0700 [thread overview]
Message-ID: <858quct18w.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <ZxvzB74fuMOmw5c+@orsosgc001>
On Fri, 25 Oct 2024 12:35:35 -0700, Umesh Nerlige Ramappa wrote:
>
Hi Umesh,
> On Fri, Oct 25, 2024 at 11:52:05AM -0700, Ashutosh Dixit wrote:
> > Verify OA syncs signal correctly in open and change config code
> > paths. Verify with different types of sync objects as well as by both
> > waiting and skipping the wait for syncs to signal.
> >
> > v2: Significantly expand oa syncs testing as described above
>
> Are we just enabling output sync for the OA use case, as in, user can only
> wait for the OA configuration to complete, but cannot control when the OA
> config starts?
No, both input and output syncs are implemented in the kernel. But this
patch only adds tests for the output syncs. I am tracking writing tests for
input syncs elsewhere.
Input syncs are also straightforward, xe_sync_entry_add_deps() basically
does that for you, you just need to call that function from the right
place. The output sync's are quite tricky and I have fixed many uaf bugs
with these tests.
> Which is what existed earlier, so it should be fine either ways.
You need both input and output syncs for it to be useful (that allows
pipelining the workload while keeping it sync'd with a particular OA
config). Mesa is using and have tested both.
>
> LGTM,
>
> Reviewed-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Thanks.
--
Ashutosh
next prev parent reply other threads:[~2024-10-25 19:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 18:52 [PATCH i-g-t 0/2] tests/intel/oa: Tests for OA syncs Ashutosh Dixit
2024-10-25 18:52 ` [PATCH i-g-t 1/2] drm-uapi/xe: Sync with OA syncs uapi update Ashutosh Dixit
2024-10-25 19:36 ` Umesh Nerlige Ramappa
2024-10-28 15:16 ` Kamil Konieczny
2024-10-29 19:38 ` Dixit, Ashutosh
2024-10-25 18:52 ` [PATCH i-g-t 2/2] tests/intel/xe_oa: Tests for OA syncs Ashutosh Dixit
2024-10-25 19:35 ` Umesh Nerlige Ramappa
2024-10-25 19:45 ` Dixit, Ashutosh [this message]
2024-10-25 22:02 ` ✓ Fi.CI.BAT: success for tests/intel/oa: Tests for OA syncs (rev4) Patchwork
2024-10-25 22:28 ` ✓ CI.xeBAT: " Patchwork
2024-10-27 12:56 ` ✗ CI.xeFULL: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-10-30 2:53 [PATCH i-g-t v5 0/2] tests/intel/oa: Tests for OA syncs Ashutosh Dixit
2024-10-30 2:53 ` [PATCH i-g-t 2/2] tests/intel/xe_oa: " Ashutosh Dixit
2024-10-30 12:54 ` Kamil Konieczny
2024-10-31 2:11 ` Dixit, Ashutosh
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=858quct18w.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=umesh.nerlige.ramappa@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