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

[fcu/ras] RAS Update Regression #341

Merged
merged 1 commit into from
Jul 25, 2019
Merged

[fcu/ras] RAS Update Regression #341

merged 1 commit into from
Jul 25, 2019

Conversation

bkorpan
Copy link
Contributor

@bkorpan bkorpan commented Jul 18, 2019

Type of change: other enhancement

Impact: rtl refactoring

Development Phase: implementation

Release Notes
Don't tell the RAS about planned redirects in f3; bad for QoR.

Copy link
Contributor

@jerryz123 jerryz123 left a comment

Choose a reason for hiding this comment

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

I guess the RAS will remain disfunctional for now

@bkorpan
Copy link
Contributor Author

bkorpan commented Jul 25, 2019

I guess the RAS will remain disfunctional for now

It sorta works. This particular signal was one of many hacks I recently added to prevent erroneous pops from corrupting the RAS in some common cases. Even with this, it still happens sometimes. I figure RAS updates should end up being decided by the branch checker and performed in F4, using the BTB causes too many problems.

@bkorpan bkorpan merged commit 7796d9f into master Jul 25, 2019
@bkorpan bkorpan deleted the ras-qor branch February 6, 2020 17:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants