[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241023074237.8013-B-hca@linux.ibm.com>
Date: Wed, 23 Oct 2024 09:42:37 +0200
From: Heiko Carstens <hca@...ux.ibm.com>
To: David Hildenbrand <david@...hat.com>
Cc: Alexander Egorenkov <egorenar@...ux.ibm.com>, 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, 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()
On Mon, Oct 21, 2024 at 04:45:59PM +0200, David Hildenbrand wrote:
> For my purpose (virtio-mem), it's sufficient to only support "kexec
> triggered kdump" either way, so I don't care.
>
> So for me it's good enough to have
>
> bool is_kdump_kernel(void)
> {
> return oldmem_data.start;
> }
>
> And trying to document the situation in a comment like powerpc does :)
Then let's go forward with this, since as Alexander wrote, this is returning
what is actually happening. If this is not sufficient or something breaks we
can still address this.
Powered by blists - more mailing lists