Skip to content

Conversation

@benyamin-codez
Copy link
Contributor

Introduces a Registry read capability:

  1. Implemented in VioStorReadRegistryParameter()
  2. Requires neo helper CopyBufferToAnsiString()
  3. Adds capacity to both detect and read DWORD values in:
    (a) HKLM\SYSTEM\CurrentControlSet\Services\viostor\Paramaters\Device
    (b) HKLM\SYSTEM\CurrentControlSet\Services\viostor\Paramaters\Device(d) (NOT WORKING)
  4. Also supports per-HBA values for \Parameters\Device\Valuename_123 when the \Parameters\Device(d) key is unavailable (presently broken)
  5. Adds TRACE_REGISTRY WPP tracing flag

Introduces a Registry read capability:

1. Implemented in VioStorReadRegistryParameter()
2. Requires neo helper CopyBufferToAnsiString()
3. Adds capacity to both detect and read DWORD values in:
   (a) HKLM\SYSTEM\CurrentControlSet\Services\viostor\Paramaters\Device
   (b) HKLM\SYSTEM\CurrentControlSet\Services\viostor\Paramaters\Device(d) NOT WORKING
4. Also supports per-HBA values for \Parameters\Device\Valuename_123
   when the \Parameters\Device(d) key is unavailable (presently broken)
5. Adds TRACE_REGISTRY WPP tracing flag

Signed-off-by: benyamin-codez <[email protected]>
@benyamin-codez
Copy link
Contributor Author

Everyone pleased enough with this one?

Not having a solution for the issue with the built-in \Parameters\Device(d) per-HBA mechanism is not ideal.
I might raise a new issue (bug) for that so as to not get hung up on it here.
Once resolved, we should consider employing registry setting migration via an installer CustomAction.

Did anyone have any comments about the in-line FIXME notes or related comments...?
...as to content and any prudent trimming or the like?

@YanVugenfirer
Copy link
Collaborator

Let's wait for @vrozenfe review

@YanVugenfirer
Copy link
Collaborator

[Jenkins CI]: Can one of the admins verify this patch?

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