Thread (72 messages) 72 messages, 9 authors, 2014-11-17
STALE4225d
Revisions (8)
  1. v1 [diff vs current]
  2. v1 [diff vs current]
  3. v1 [diff vs current]
  4. v1 [diff vs current]
  5. v1 [diff vs current]
  6. v1 [diff vs current]
  7. v1 current
  8. v1 [diff vs current]

[PATCH 00/10] arm64 kexec kernel patches V5

From: Dave Young <hidden>
Date: 2014-11-13 08:37:06
Also in: kexec

On 10/31/14 at 04:25pm, Geoff Levand wrote:
Hi Dave,

Thanks for testing.

On Fri, 2014-10-31 at 15:52 +0800, Dave Young wrote:
quoted
I tested your patches. The macihne is using spin-table cpu enable method
so I tried maxcpus=1 as you suggested.

There's below issues for me, thoughts?

1. For acpi booting there's no /proc/device-tree so kexec can not find dtb
to use.
You can supply a DTB with the kexec --dtb option, then kexec will not need
/proc/device-tree.  Please try if you can and let me know what happens.
In your kexec-tools code, by default it will create dtb1 from procfs, as for external
--dtb it will be dtb2 for comparing with dtb1.

Since dtb1 is a must so it will not work without /proc/device-tree.

There had some discussion about this in the thread. But I think we have no
conclusion where to go.

There maybe below possibilities:
1) unflattern dtb both for EFI/acpi booting even if acpi boot does not need it.

2) copy the bootloader passed dtb stub to somewhere, and export the stub to
 userspace ie. in debugfs or procfs
 like /proc/saved_dtb 

Thoughts to continue the discuss?

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