From: David Hildenbrand <david@redhat.com>
To: Alexander Egorenkov <egorenar@linux.ibm.com>,
linux-kernel@vger.kernel.org
Cc: linux-s390@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>
Subject: Re: [PATCH v3] s390/kdump: make is_kdump_kernel() consistently return "true" in kdump environments only
Date: Wed, 23 Oct 2024 14:22:18 +0200 [thread overview]
Message-ID: <7da9f43f-e2a8-4079-8b1d-d7b16d8f388e@redhat.com> (raw)
In-Reply-To: <87ttd3t3v7.fsf@li-0ccc18cc-2c67-11b2-a85c-a193851e4c5d.ibm.com>
On 23.10.24 14:12, Alexander Egorenkov wrote:
> Hi David,
>
>
> David Hildenbrand <david@redhat.com> writes:
>
>> Similarly provide a custom is_kdump_kernel() implementation that will only
>> return "true" in kdump environments, and will do so consistently during
>> boot.
>>
>> Update the documentation of is_dump_available().
>
> A small typo here:
>
> is_dump_available() -> dump_available()
>
>> @@ -587,16 +587,16 @@ int smp_store_status(int cpu)
>> * with sigp stop-and-store-status. The firmware or the boot-loader
>> * stored the registers of the boot CPU in the absolute lowcore in the
>> * memory of the old system.
>> - * 3) kdump and the old kernel did not store the CPU state,
>> - * or stand-alone kdump for DASD
>> - * condition: OLDMEM_BASE != NULL && !is_kdump_kernel()
>> + * 3) kdump or stand-alone kdump for DASD
>> + * condition: OLDMEM_BASE != NULL && !is_ipl_type_dump() == false
>
> Here is a typo in the condition, a redundant '!' before is_ipl_type_dump().
>
Thanks for catching these! Too much going back and forth ... :)
> Otherwise, looks very good to me.
Thanks for the fast review. I assume these can be fixed up when
applying. But please let me know if a v3 is preferred, and I can send
one after waiting a couple of days.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-10-23 12:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 9:06 [PATCH v3] s390/kdump: make is_kdump_kernel() consistently return "true" in kdump environments only David Hildenbrand
2024-10-23 12:12 ` Alexander Egorenkov
2024-10-23 12:22 ` David Hildenbrand [this message]
2024-10-23 12:53 ` Heiko Carstens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7da9f43f-e2a8-4079-8b1d-d7b16d8f388e@redhat.com \
--to=david@redhat.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=egorenar@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=svens@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox