Skip to content

Consider removing PD access to their own VSpace (or making it optional) #518

@midnightveil

Description

@midnightveil

// Allow PD to access their own VSpace for ops such as cache cleaning on ARM.
caps_to_insert_to_pd_cspace.push(capdl_util_make_cte(
PD_VSPACE_CAP_IDX as u32,
capdl_util_make_page_table_cap(pd_vspace_obj_id),
));

On ARM, there are user-level cache operations that are faster and better to use in basically every way, so I don't think this is ever needed.

Other architectures I think would be similar.

However, this would be a breaking change.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions