On Wed, Jul 06, 2016 at 10:44:27AM -0700, Geoff Levand wrote: > On Wed, 2016-07-06 at 16:52 +0900, AKASHI Takahiro wrote: > > --- a/Documentation/kdump/kdump.txt > > +++ b/Documentation/kdump/kdump.txt > > @@ -18,7 +18,7 @@ memory image to a dump file on the local disk, or across the network to > > a remote system. > > > > Kdump and kexec are currently supported on the x86, x86_64, ppc64, ia64, > > -s390x and arm architectures. > > +s390x, arm and arm64 architectures. > > > > When the system kernel boots, it reserves a small section of memory for > > the dump-capture kernel. This ensures that ongoing Direct Memory Access > > @@ -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 at the dump-capture kernel will not be enabled > > kvm of the dump-capture kernel > > > + on non-VHE system even if it is configured. This is because we have > > on non-VHE systems > > > + no chance to reset CPU state to EL2 on panic. > > This is because the CPU state cannot be reset to EL2 on panic. Thanks :) -Takahiro AKASHI > >
