[siemens/jailhouse] a9bf0d: tools: jailhouse: Do not dump console on enabling ...

瀏覽次數:3 次
跳到第一則未讀訊息

GitHub

未讀,
2017年4月28日 凌晨2:19:252017/4/28
收件者:jailho...@googlegroups.com
Branch: refs/heads/next
Home: https://github.com/siemens/jailhouse
Commit: a9bf0d3512a8879e9e5383111172e1c1c0a1352b
https://github.com/siemens/jailhouse/commit/a9bf0d3512a8879e9e5383111172e1c1c0a1352b
Author: Jan Kiszka <jan.k...@siemens.com>
Date: 2017-04-28 (Fri, 28 Apr 2017)

Changed paths:
M tools/jailhouse.c

Log Message:
-----------
tools: jailhouse: Do not dump console on enabling errors

We cannot reliably tell apart errors that happen before we call into the
hypervisor binary from those that happen after that. The latters may
have left some relevant messages in the console buffer, but the former
can make us dump confusing messages from a previous Jailhouse run.

Better let the user decide if the console content should be shown via an
explicit invocation of "jailhouse console".

Reported-and-suggested-by: Ralf Ramsauer <ralf.r...@oth-regensburg.de>
Signed-off-by: Jan Kiszka <jan.k...@siemens.com>


Commit: acb65deec620edada0e54236c48199ad3e572de6
https://github.com/siemens/jailhouse/commit/acb65deec620edada0e54236c48199ad3e572de6
Author: Jan Kiszka <jan.k...@siemens.com>
Date: 2017-04-28 (Fri, 28 Apr 2017)

Changed paths:
M tools/jailhouse.c

Log Message:
-----------
tools: jailhouse: Rework console dump

Fold dump_console into its only remaining user and add some more error
messages.

Signed-off-by: Jan Kiszka <jan.k...@siemens.com>


Compare: https://github.com/siemens/jailhouse/compare/3dde793c0e94...acb65deec620

GitHub

未讀,
2017年4月29日 凌晨1:23:002017/4/29
收件者:jailho...@googlegroups.com
Branch: refs/heads/coverity_scan
回覆所有人
回覆作者
轉寄
0 則新訊息