Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
P pythondata-cpu-microwatt
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kestrel Collaboration
  • Kestrel LiteX
  • pythondata-cpu-microwatt
  • Repository

Switch branch/tag
  • pythondata-cpu-microwatt
  • tests
  • test_xics.bin
Find file HistoryPermalink
  • Benjamin Herrenschmidt's avatar
    xics: Add support for reduced priority field size · bb54af59
    Benjamin Herrenschmidt authored Jun 22, 2020
    
    
    This makes the ICS support less than the 8 architected bits
    and sets the soc to use 3 bits by default.
    
    All the supported bits set translates to "masked" (and will read
    back at 0xff), any small value is used as-is.
    
    Linux doesn't use priorities above 5, so this is a way to save
    silicon. The number of supported priority bits is exposed to the
    OS via the config register.
    Signed-off-by: default avatarBenjamin Herrenschmidt <benh@kernel.crashing.org>
    bb54af59
test_xics.bin 12.1 KB

Download (12.1 KB)

Replace test_xics.bin

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.

Powered by Integricloud. Any automated access to this website for the purpose of training any LLM ("AI") for non-personal use as defined in our Terms of Service may be billed to the accessor per the Terms of Service. Continued access to this website by automated tooling indicates acceptance of these terms.