linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-s390@vger.kernel.org, Vasily Gorbik <gor@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Philipp Rudo <prudo@linux.ibm.com>,
	Michael Holzheu <holzheu@linux.vnet.ibm.com>
Subject: Re: [PATCH RFC 2/2] s390/mm: don't set ARCH_KEEP_MEMBLOCK
Date: Mon, 29 Jun 2020 15:02:30 +0200	[thread overview]
Message-ID: <1d9b431a-58cb-8b5f-cb3f-5656a3032e34@redhat.com> (raw)
In-Reply-To: <20200629124432.GE4468@osiris>

On 29.06.20 14:44, Heiko Carstens wrote:
> On Fri, Jun 26, 2020 at 06:32:15PM +0200, Heiko Carstens wrote:
>> On Fri, Apr 17, 2020 at 05:01:51PM +0200, David Hildenbrand wrote:
>>> Commit 50be63450728 ("s390/mm: Convert bootmem to memblock") mentions
>>> 	"The original bootmem allocator is getting replaced by memblock. To
>>> 	cover the needs of the s390 kdump implementation the physical
>>> 	memory list is used."
>>>
>>> zcore was converted to use resources instead of memblocks.
>>> memblock_discard() will *not* mess with "physmem", only with "memory" and
>>> "reserved" memblocks. So, that data will stay after early boot, to be
>>> used in arch/s390/kernel/crash_dump.c to create the ELF header from
>>> inside the 2nd (a.k.a. dumping) kernel.
>>>
>>> We no longer need ARCH_KEEP_MEMBLOCK.
>>>
>>> Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
>>> Cc: Vasily Gorbik <gor@linux.ibm.com>
>>> Cc: Christian Borntraeger <borntraeger@de.ibm.com>
>>> Cc: Philipp Rudo <prudo@linux.ibm.com>
>>> Cc: Michael Holzheu <holzheu@linux.vnet.ibm.com>
>>> Signed-off-by: David Hildenbrand <david@redhat.com>
>>> ---
>>>  arch/s390/Kconfig | 1 -
>>>  1 file changed, 1 deletion(-)
>>
>> Applied, thanks!
> 
> Hmm, this triggers:

Ah, I see, will have a look. Weird I didn't notice that ...

Thanks!



-- 
Thanks,

David / dhildenb



  reply	other threads:[~2020-06-29 13:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-17 15:01 [PATCH RFC 0/2] " David Hildenbrand
2020-04-17 15:01 ` [PATCH RFC 1/2] s390/zcore: traverse resources instead of memblocks David Hildenbrand
2020-06-10 11:45   ` Heiko Carstens
2020-06-19 12:47     ` Philipp Rudo
2020-06-19 12:49       ` David Hildenbrand
2020-04-17 15:01 ` [PATCH RFC 2/2] s390/mm: don't set ARCH_KEEP_MEMBLOCK David Hildenbrand
2020-06-26 16:32   ` Heiko Carstens
2020-06-29 12:44     ` Heiko Carstens
2020-06-29 13:02       ` David Hildenbrand [this message]
2020-04-29 14:55 ` [PATCH RFC 0/2] " David Hildenbrand

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=1d9b431a-58cb-8b5f-cb3f-5656a3032e34@redhat.com \
    --to=david@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=holzheu@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=prudo@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