On 08/30/2017 10:53 AM, Laszlo Ersek wrote:
Repo: https://github.com/lersek/edk2.git Branch: sev_debug_messages I've now looked at quite a bit of SEV-related DEBUG messages, and I find them really hard to read, and to process with command line utilities like grep, sort, uniq. For example, shell pipelines should be possible to construct with these utilities to collect decrypt/encrypt operations, in chronological order, grouped by address ever decrypted. The log should also be human-readable as much as possible -- it shouldn't be redundant, but all information for forward- and back-referencing should be available. I propose this series for the above improvements. Cc: Brijesh Singh <brijesh.si...@amd.com> Cc: Jordan Justen <jordan.l.jus...@intel.com>
Very nice improvement in debug message, thank you ! Reviewed-by: Brijesh Singh <brijesh.si...@amd.com> Tested-by: Brijesh Singh <brijesh.si...@amd.com> _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
