msm-4.14/Documentation
Boris Ostrovsky 588c0f3282 x86/xen: Return from panic notifier
[ Upstream commit c6875f3aacf2a5a913205accddabf0bfb75cac76 ]

Currently execution of panic() continues until Xen's panic notifier
(xen_panic_event()) is called at which point we make a hypercall that
never returns.

This means that any notifier that is supposed to be called later as
well as significant part of panic() code (such as pstore writes from
kmsg_dump()) is never executed.

There is no reason for xen_panic_event() to be this last point in
execution since panic()'s emergency_restart() will call into
xen_emergency_restart() from where we can perform our hypercall.

Nevertheless, we will provide xen_legacy_crash boot option that will
preserve original behavior during crash. This option could be used,
for example, if running kernel dumper (which happens after panic
notifiers) is undesirable.

Reported-by: James Dingwall <james@dingwall.me.uk>
Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
2019-11-06 12:43:13 +01:00
..
2019-10-29 09:17:10 +01:00
2017-09-07 21:11:05 -07:00
2017-10-19 22:26:11 -04:00
2018-02-22 15:42:24 +01:00
2017-08-30 15:18:24 -06:00
2017-09-04 00:06:02 +02:00
2017-07-07 13:55:45 -07:00
2017-07-06 10:56:51 -07:00
2017-08-25 17:58:34 +03:00
2017-07-07 14:04:47 -07:00
2017-07-14 13:51:29 -06:00
2019-06-09 09:18:17 +02:00
2017-08-19 11:02:53 -07:00
2017-07-14 13:51:34 -06:00
2017-07-14 13:51:40 -06:00
2017-07-14 13:51:42 -06:00
2017-07-14 13:51:43 -06:00
2017-07-14 13:51:43 -06:00
2017-07-14 13:51:45 -06:00
2017-07-14 13:51:45 -06:00
2017-07-14 13:51:46 -06:00
2017-07-14 13:57:58 -06:00
2017-07-14 13:57:59 -06:00
2017-07-06 08:23:30 +02:00
2017-07-07 13:14:14 +02:00
2017-07-14 13:58:04 -06:00
2017-07-14 13:58:08 -06:00
2017-07-14 13:58:14 -06:00
2017-07-14 13:58:10 -06:00
2017-07-14 13:58:11 -06:00