Re: [Xen-devel] XSM SILO boot time spew

["Xin Li (Talons)" <xin.li@xxxxxxxxxx>]

> -----Original Message-----
> From: Daniel De Graaf [mailto:dgdegra@xxxxxxxxxxxxx]
> Sent: Thursday, November 8, 2018 1:53 AM
> To: Xin Li (Talons) <xin.li@xxxxxxxxxx>; Andrew Cooper
> <Andrew.Cooper3@xxxxxxxxxx>
> Cc: Xen-devel List <xen-devel@xxxxxxxxxxxxx>
> Subject: Re: XSM SILO boot time spew

> If SILO is a good example of what a potential third XSM module would look 
> like,
> it's probably better to just remove the printing and allow the dummy module's
> hooks to fill in any null values in the xsm_operations structure.  The 
> printing
> part was written with FLASK and ACM in mind, which both intended to hook
> everything and might add new hooks without changing the other.
> 
> Another possible solution would be to add a bool parameter to register_xsm
> that disables the warnings instead of checking the pointer value, but that 
> feels
> like overkill to me; we still only have two XSM modules.

OK. I will just remove the printing.

Best regards

Xin(Talons) Li
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel