Skip to content

Automatically allow OSs to create dedicated memory allocators #138

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Automatically allow OSs to create dedicated memory allocators #138

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b6a4c5a
schemas: reserved-memory: Add ECC parameters
mripard May 15, 2024
80251dc
schemas: reserved-memory: Add export property
mripard May 15, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions dtschema/schemas/reserved-memory/reserved-memory.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,26 @@ properties:
Address and Length pairs. Specifies regions of memory that are
acceptable to allocate from.

ecc-detection-bits:
default: 0
description: |
If present, this indicates the number of bits of memory error
which can be detected and reported by the Error-Correction Code
(ECC) memory subsystem (typically 0, 1 or 2).

ecc-correction-bits:
default: 0
description: |
If present, this indicates the number of bits of memory error
which can be corrected by the Error-Correction Code (ECC) memory
subsystem (typically 0, 1 or 2).

export:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this be mutually exclusive with no-map and reusable?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's one of the things I wasn't too sure about. I don't think it's mutually exclusive with no-map per se. If we take the Linux example, we can totally create dma-buf from memory that isn't accessible to the CPU.

reusable however looks like it could be made mutually exclusive with it.

type: boolean
description: >
The operating system can use the memory to create special-purpose
allocators instead of solely dedicating it to the device.

iommu-addresses:
$ref: /schemas/types.yaml#/definitions/phandle-array
description: >
Expand Down