+1 I also would add there may be some HII strings that are hidden from user interfaces, and reflect settings for field service or troubleshooting, and that a mass export to the OS may expose these settings to OS runtime code and possibly applications.
-----Original Message----- From: edk2-devel [mailto:[email protected]] On Behalf Of Andrew Fish Sent: Tuesday, February 16, 2016 10:37 AM To: Brian J. Johnson <[email protected]> Cc: Dandan Bi <[email protected]>; [email protected]; Eric Dong <[email protected]>; Liming Gao <[email protected]> Subject: Re: [edk2] [patch] MdeModulePkg: Make HII configuration settings available to OS runtime > On Feb 16, 2016, at 8:33 AM, Brian J. Johnson <[email protected]> wrote: > > On 02/16/2016 12:58 AM, Dandan Bi wrote: >> This feature is aimed to allow OS make use of the HII database during >> runtime. In this case, the contents of the HII Database is exported >> to a buffer. The pointer to the buffer is placed in the EFI System >> Configuration Table, where it can be retrieved by an OS application. >> >> Export the configuration data and contents of HiiDatabase when driver >> add package, update package and remove package. >> For string and image may also need to update the contents of >> HiiDatabase when NewString/SetString, NewImage/SetImage. >> >> Cc: Liming Gao <[email protected]> >> Cc: Eric Dong <[email protected]> >> Contributed-under: TianoCore Contribution Agreement 1.0 >> Signed-off-by: Dandan Bi <[email protected]> ... > > Please make this behavior selectable via a PCD. HII operations are very > expensive, especially on simulators. I don't want to pay the export time > every time a package is added or string is changed. Also, platforms should > be able to decide if they want to offer this data to the OS. > +1 I would want to opt out to NOT take the memory away from the OS if the platform did not care about the feature. Thanks, Andrew Fish > Why not just export the data once, using a "ready to boot" event hook? > > Thanks, > -- > > Brian J. Johnson > > -------------------------------------------------------------------- > > My statements are my own, are not authorized by SGI, and do not > necessarily represent SGI's positions. > _______________________________________________ > edk2-devel mailing list > [email protected] > https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
