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.

Sign up for GitHub

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

Jump to bottom

[L0] Maintain Lock of Queue while syncing the Last Command Event and update Last Command Event only if matching #1749

Merged
merged 2 commits into from
Jun 14, 2024
Merged

[L0] Maintain Lock of Queue while syncing the Last Command Event and update Last Command Event only if matching #1749

merged 2 commits into from
Jun 14, 2024

Commits on Jun 12, 2024

  1. [L0] Maintain Lock of Queue while syncing the Last Command Event 

    - To avoid usecases where the LastcommandEvent could be updated in
  another thread and a thread can be expecting the Queue Wait to include
this event, then hold the queue lock such that the last command event
remains unchanged during synchronization.

Signed-off-by: Neil R. Spruit <neil.r.spruit@intel.com>
    @nrspruit
    nrspruit committed Jun 12, 2024
    Configuration menu
    Copy the full SHA
    6db9291 View commit details
    Browse the repository at this point in the history

Commits on Jun 13, 2024

  1. [L0] Verify the LastCommandEvent is unchanged after sync before nullptr 

    Signed-off-by: Neil R. Spruit <neil.r.spruit@intel.com>
    @nrspruit
    nrspruit committed Jun 13, 2024
    Configuration menu
    Copy the full SHA
    a461778 View commit details
    Browse the repository at this point in the history