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

fix: Removed the condition variable check from Sysman Memory CTS #122

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

pratikbariintel
Copy link
Contributor

@pratikbariintel pratikbariintel commented Dec 16, 2024

During the call to fetch the memory and the RAS states, the condition variable check has been removed.

Related-To: VLCLJ-2343

Signed-off-by: Pratik Bari [email protected]

During the call to fetch the memory and the RAS states, the condition
variable check has been removed.

Related-To: VLCLJ-2343

Signed-off-by: Pratik Bari <[email protected]>
@pratikbariintel pratikbariintel changed the title fix: Removed the condition variable check from the ULT @pratikbariintel fix: Removed the condition variable check from Sysman Memory CTS Dec 17, 2024
@pratikbariintel pratikbariintel changed the title @pratikbariintel fix: Removed the condition variable check from Sysman Memory CTS fix: Removed the condition variable check from Sysman Memory CTS Dec 17, 2024
@vishnu-khanth
Copy link
Contributor

The issue is previously deadlock was happening if one of the threads exit when handles not found. Is this right ?

for (auto mem_handle : mem_handles) {
ASSERT_NE(nullptr, mem_handle);
lzt::get_mem_state(mem_handle);
}
lock.unlock();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

now as per the changes we have get_mem_state & get_ras_state happening serially one after the other.

But do need to fetch mem state & ras state concurrently ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As we are launching get_mem_state and get_ras_state in the threads, it does not guarantee that one will run before/after the latter. Have removed the mutex lock/unlocks now which will facilitate concurrency.

@pratikbariintel
Copy link
Contributor Author

The issue is previously deadlock was happening if one of the threads exit when handles not found. Is this right ?

Yes

Copy link
Contributor

@vishnu-khanth vishnu-khanth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

During the call to fetch the memory and the RAS states, the condition
variable check has been removed.

Related-To: VLCLJ-2343

Signed-off-by: Pratik Bari <[email protected]>
During the call to fetch the memory and the RAS states, the condition
variable check has been removed.

Related-To: VLCLJ-2343

Signed-off-by: Pratik Bari <[email protected]>
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.

2 participants