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

Add rfm history to allowed falconctl options #1582

Merged
merged 1 commit into from
Feb 6, 2024

Conversation

iamharlie
Copy link
Contributor

We learned here that there's a third mode (aside kernel and reduced functionality) that we do not currently consider. We can determine this third mode, user mode, by looking at the rfm history.

This PR adds --rfm-history to the allowedOptions for falconctl, which looks like this:

rfm-history={[0 (newest)] kernel backend, not in RFM, rfm-reason=None, code=0x0; [1] kernel backend, in RFM, rfm-reason=Modules file was not found, code=0xC0000034; [2] kernel backend, in RFM, rfm-reason=Modules file was not found, code=0xC0000034}.```

@CLAassistant
Copy link

CLAassistant commented Feb 6, 2024

CLA assistant check
All committers have signed the CLA.

@iamharlie iamharlie added this pull request to the merge queue Feb 6, 2024
Merged via the queue into main with commit 6e83279 Feb 6, 2024
27 checks passed
@iamharlie iamharlie deleted the harlie/falcon-rfm-history branch February 6, 2024 17:43
James-Pickett pushed a commit to James-Pickett/launcher that referenced this pull request Feb 7, 2024
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.

5 participants