Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Starting trace module using a broadcast network for XDP Client #8455

Merged
merged 4 commits into from
Sep 30, 2024

Conversation

jyothees99
Copy link
Collaborator

Problem solved by the commit

Trace modules are being started at different times. Because of this, trace start can't be used to verify timer synchronization.

How problem was solved, alternative solutions (if any) and why they were rejected

A broadcast network is used to start the trace modules. Alternative solution is to start trace module using true event sequentially. But the differences between timers of trace modules will be hundreds of cylces. With broadcast network, the difference is too less.

What has been tested and how, request additional testing if necessary

On client I have verified one model. The timers were in sync and trace module starts with broadcast event.

@gbuildx
Copy link
Collaborator

gbuildx commented Sep 25, 2024

Can one of the admins verify this patch?

Signed-off-by: jyothees <Jyotheeswar.Ganne@amd.com>
…pl to avoid calling get_aie_trace_settings_trace_start_broadcast ini settings multiple times

Signed-off-by: jyothees <Jyotheeswar.Ganne@amd.com>
…itions

Signed-off-by: jyothees <Jyotheeswar.Ganne@amd.com>
…f XDP client trace

Signed-off-by: jyothees <Jyotheeswar.Ganne@amd.com>
@jvillarre jvillarre merged commit 9b149a4 into Xilinx:master Sep 30, 2024
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants