Kconfig/menuconfig tailoring of XSM policy

Description

With ongoing work for disaggregation of OpenXT components (e.g. USB and storage VMs), optional layers (e.g. single VM, multidomain, edge/server) and customization by derivatives, there is a corresponding need to tailor XSM policy for the subset of components in specific appliance.

This is a ticket to investigate:

  • OE support for XSM policy tailoring, e.g. for each VM image

  • XSM policy for specific components or groups of components

  • Usability of menuconfig/kconfig for tailoring XSM policy

  • Initial use cases for OpenXT, derivatives and upstream Xen (e.g. Argo, stubdomains, NDVM, IOMMU handling, HAP)

Validation Steps

None

Assignee

Unassigned

Reporter

Rich Persaud

Labels

None

QA Assignee

None

QA Image URL

None

Components

Priority

Major
Configure