Thread (42 messages) 42 messages, 9 authors, 2016-11-01
STALE3508d
Revisions (12)
  1. v22 [diff vs current]
  2. v26 [diff vs current]
  3. v26 current
  4. v26 [diff vs current]
  5. v26 [diff vs current]
  6. v27 [diff vs current]
  7. v28 [diff vs current]
  8. v29 [diff vs current]
  9. v30 [diff vs current]
  10. v32 [diff vs current]
  11. v34 [diff vs current]
  12. v35 [diff vs current]

[PATCH v26 6/7] arm64: kdump: update a kernel doc

From: james.morse@arm.com (James Morse)
Date: 2016-09-16 16:08:28
Also in: kexec

Hi Akashi,

On 07/09/16 05:29, AKASHI Takahiro wrote:
This patch adds arch specific descriptions about kdump usage on arm64
to kdump.txt.
quoted hunk ↗ jump to hunk
diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt
quoted hunk ↗ jump to hunk
@@ -249,6 +249,13 @@ Dump-capture kernel config options (Arch Dependent, arm)
 
     AUTO_ZRELADDR=y
 
+Dump-capture kernel config options (Arch Dependent, arm64)
+----------------------------------------------------------
+
+- Please note that kvm of the dump-capture kernel will not be enabled
+  on non-VHE systems even if it is configured. This is because the CPU
+  cannot be reset to EL2 on panic.
Nit:
cannot be -> will not be

We could try to do this, but its more code that could prevent us reaching the
kdump kernel, so we choose not to.

quoted hunk ↗ jump to hunk
@@ -370,6 +381,9 @@ For s390x:
 For arm:
 	"1 maxcpus=1 reset_devices"
 
+For arm64:
+	"1 maxcpus=1 reset_devices"
+
'maxcpus=1' is a bit fragile. Since 44dbcc93ab67145 ("arm64: Fix behavior of
maxcpus=N") udev on ubuntu vivid (running on Juno) has taken it upon itself to
bring the secondary cores online, even when booted with 'maxcpus=1'.

Can we change the recomendation to "1 nosmp reset_devices"?


Thanks,

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