On 31.05.2022 20:20, Daniel P. Smith wrote: > It is possible to select a few different build configurations that results in > the unnecessary walking of the boot module list looking for a policy module. > This specifically occurs when the flask policy is enabled but either the dummy > or the SILO policy is selected as the enforcing policy. This is not ideal for > configurations like hyperlaunch and dom0less when there could be a number of > modules to be walked or doing an unnecessary device tree lookup. > > This patch introduces the policy_file_required flag for tracking when an XSM > policy module requires a policy file. Only when the policy_file_required flag > is set to true, will XSM search the boot modules for a policy file. > > Signed-off-by: Daniel P. Smith <[email protected]> > Reviewed-by: Jan Beulich <[email protected]> > --- > xen/xsm/xsm_core.c | 16 ++++++++++++++-- > 1 file changed, 14 insertions(+), 2 deletions(-)
FTAOD my (later) v3 comments still apply; v4 simply appeared too quickly. Jan
