Thread (30 messages) 30 messages, 5 authors, 2017-01-24
STALE3424d
Revisions (14)
  1. v1 [diff vs current]
  2. v22 [diff vs current]
  3. v23 [diff vs current]
  4. v27 [diff vs current]
  5. v28 [diff vs current]
  6. v28 [diff vs current]
  7. v28 [diff vs current]
  8. v29 [diff vs current]
  9. v29 [diff vs current]
  10. v29 [diff vs current]
  11. v29 current
  12. v32 [diff vs current]
  13. v34 [diff vs current]
  14. v35 [diff vs current]

[PATCH v29 4/9] arm64: kdump: implement machine_crash_shutdown()

From: Will Deacon <hidden>
Date: 2017-01-11 10:54:05
Also in: kexec

On Wed, Jan 11, 2017 at 03:36:28PM +0900, AKASHI Takahiro wrote:
On Tue, Jan 10, 2017 at 11:32:48AM +0000, Will Deacon wrote:
quoted
On Wed, Dec 28, 2016 at 01:36:01PM +0900, AKASHI Takahiro wrote:
quoted
@@ -22,6 +25,7 @@
 extern const unsigned char arm64_relocate_new_kernel[];
 extern const unsigned long arm64_relocate_new_kernel_size;
 
+static bool in_crash_kexec;
Do you actually need this bool? Why not call kexec_crash_loaded() instead?
The two have different meanings:
"in_crash_kexec" indicates that kdump is taking place, while
kexec_crash_loaded() tells us only whether crash dump kernel has been
loaded or not.

It is crucial to distinguish them especially for machine_kexec()
which can be called on normal kexec even if kdump has been set up.
Ah, I see. So how about just doing:

  if (kimage == kexec_crash_image)

in machine_kexec?

Will
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help