[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87wmhzt6ey.fsf@li-0ccc18cc-2c67-11b2-a85c-a193851e4c5d.ibm.com>
Date: Wed, 23 Oct 2024 13:17:25 +0200
From: Alexander Egorenkov <egorenar@...ux.ibm.com>
To: David Hildenbrand <david@...hat.com>
Cc: agordeev@...ux.ibm.com, akpm@...ux-foundation.org,
borntraeger@...ux.ibm.com, cohuck@...hat.com, corbet@....net,
eperezma@...hat.com, frankja@...ux.ibm.com, gor@...ux.ibm.com,
hca@...ux.ibm.com, imbrenda@...ux.ibm.com, jasowang@...hat.com,
kvm@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-s390@...r.kernel.org, mcasquer@...hat.com, mst@...hat.com,
svens@...ux.ibm.com, thuth@...hat.com, virtualization@...ts.linux.dev,
xuanzhuo@...ux.alibaba.com, zaslonko@...ux.ibm.com
Subject: Re: [PATCH v2 1/7] s390/kdump: implement is_kdump_kernel()
Hi David,
David Hildenbrand <david@...hat.com> writes:
> Staring at the powerpc implementation:
>
> /*
> * Return true only when kexec based kernel dump capturing method is used.
> * This ensures all restritions applied for kdump case are not automatically
> * applied for fadump case.
> */
> bool is_kdump_kernel(void)
> {
> return !is_fadump_active() && elfcorehdr_addr != ELFCORE_ADDR_MAX;
> }
> EXPORT_SYMBOL_GPL(is_kdump_kernel);
Thanks for the pointer.
I would say power's version is semantically equivalent to what i have in
mind for s390 :) If a dump kernel is running, but not a stand-alone
one (apart from sa kdump), then it's a kdump kernel.
Regards
Alex
Powered by blists - more mailing lists