Skip to content

readme: Add CounterType and ProgrammingRestriction - #375

Open
edwarddavidbaker wants to merge 5 commits into
intel:mainfrom
edwarddavidbaker:readme-updates
Open

readme: Add CounterType and ProgrammingRestriction#375
edwarddavidbaker wants to merge 5 commits into
intel:mainfrom
edwarddavidbaker:readme-updates

Conversation

@edwarddavidbaker

@edwarddavidbaker edwarddavidbaker commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Add documentation to describe event fields CounterType and ProgrammingRestriction.

Pre-merge rendered markdown can be viewed at https://github.com/edwarddavidbaker/perfmon/tree/readme-updates#countertype .

Add documentation to describe event fields CounterType and
ProgrammingRestriction.
@edwarddavidbaker

edwarddavidbaker commented Jul 10, 2026

Copy link
Copy Markdown
Contributor Author

Thanks for drafting readme content Ryan. What do you think about the [N] indexing? Do you think adding a small mermaid diagram would help succinctly show an example?

Comment thread README.md Outdated
@rpmclaug

Copy link
Copy Markdown
Contributor

@edwarddavidbaker Ideally this document could remain legible in text editors; If there's a means to clarify the text description, let's start there.

Can you provide an example of the sort of diagram you think would help?

One possibility to help differentiate these:

flowchart

    MUX(MSRIndex-UMask
    UMask: A,B
    MSRIndex: C,D
    Counter: 0,1) --> MUY{UMask: A
    MSRIndex: C
    Counter: 0,1}
    MUX --> MUZ{UMask: B
    MSRIndex: D
    Counter: 0,1}

    MUCX(MSRIndex-UMask-Counter
    UMask: A,B
    MSRIndex: C,D
    Counter: 0,1) --> MUCY{UMask: A
    MSRIndex: C
    Counter: 0}
    MUCX --> MUCZ{UMask: B
    MSRIndex: D
    Counter: 1}
Loading

Co-authored-by: Ryan McLaughlin <ryan.p.mclaughlin@intel.com>
@edwarddavidbaker

Copy link
Copy Markdown
Contributor Author

@edwarddavidbaker Ideally this document could remain legible in text editors; If there's a means to clarify the text description, let's start there.

Can you provide an example of the sort of diagram you think would help?

One possibility to help differentiate these:

flowchart

    MUX(MSRIndex-UMask
    UMask: A,B
    MSRIndex: C,D
    Counter: 0,1) --> MUY{UMask: A
    MSRIndex: C
    Counter: 0,1}
    MUX --> MUZ{UMask: B
    MSRIndex: D
    Counter: 0,1}

    MUCX(MSRIndex-UMask-Counter
    UMask: A,B
    MSRIndex: C,D
    Counter: 0,1) --> MUCY{UMask: A
    MSRIndex: C
    Counter: 0}
    MUCX --> MUCZ{UMask: B
    MSRIndex: D
    Counter: 1}
Loading

Agreed, the direct text should be comprehensive. Your diagram is similar to what I was thinking to help visualize using JSON content. I also want to include an invalid scenario. Submitting a follow-up commit here soon.

edwarddavidbaker and others added 2 commits August 4, 2026 08:30
Add a markdown diagram to showcase a few programming restriction
valid and invalid examples.

Co-authored-by: Ryan McLaughlin <ryan.p.mclaughlin@intel.com>
Update documentation.

Co-authored-by: Ryan McLaughlin <ryan.p.mclaughlin@intel.com>
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