From: Guenter Roeck <linux@roeck-us.net>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: rppt@kernel.org, akpm@linux-foundation.org, linux-mm@kvack.org,
Paul Mackerras <paulus@ozlabs.org>, Tejun Heo <tj@kernel.org>
Subject: Re: [Patch v3] mm/memblock: remove empty dummy entry
Date: Thu, 20 Jun 2024 19:34:06 -0700 [thread overview]
Message-ID: <a2f0efdf-7e77-40f5-b74e-db76a1b284dd@roeck-us.net> (raw)
In-Reply-To: <20240621010713.cyai3pkucbp7v7r5@master>
On 6/20/24 18:07, Wei Yang wrote:
> On Thu, Jun 20, 2024 at 02:58:17PM -0700, Guenter Roeck wrote:
>> Hi,
>>
>> On Fri, Apr 05, 2024 at 01:58:21AM +0000, Wei Yang wrote:
>>> The dummy entry is introduced in the initial implementation of lmb in
>>> commit 7c8c6b9776fb ("powerpc: Merge lmb.c and make MM initialization
>>> use it.").
>>>
>>> As the comment says the empty dummy entry is to simplify the code.
>>>
>>> /* Create a dummy zero size LMB which will get coalesced away later.
>>> * This simplifies the lmb_add() code below...
>>> */
>>>
>>> While current code is reimplemented by Tejun in commit 784656f9c680
>>> ("memblock: Reimplement memblock_add_region()"). This empty dummy entry
>>> seems not benefit the code any more.
>>>
>>> Let's remove it.
>>>
>>> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
>>> CC: Paul Mackerras <paulus@ozlabs.org>
>>> CC: Tejun Heo <tj@kernel.org>
>>> CC: Mike Rapoport <rppt@kernel.org>
>>>
>>
>> With this patch in linux-next, all microblaze qemu images fail to boot. Reverting it
>> fixes the problem.
>>
>> Bisect log is attached for reference.
>>
>
> Thanks for the reporting.
>
> Would you mind running the test to take a look?
>
> It is in tools/testing/memblock. Simply make and ./main.
>
This is a silent failure. There is no console output, so the image crashes
before it gets to that point.
Building microblaze:petalogix-s3adsp1800:initrd ... running ................R............. failed (silent)
------------
qemu log:
qemu-system-microblaze: terminating on signal 15 from pid 2343410 (/bin/bash)
Guenter
next prev parent reply other threads:[~2024-06-21 2:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 1:58 Wei Yang
2024-04-08 5:44 ` Mike Rapoport
2024-04-08 12:37 ` Wei Yang
2024-04-09 5:02 ` Mike Rapoport
[not found] ` <8d6205d4-18fb-4e98-97e6-db226dcf48f3@roeck-us.net>
2024-06-21 1:07 ` Wei Yang
2024-06-21 2:34 ` Guenter Roeck [this message]
2024-06-21 23:06 ` Wei Yang
[not found] ` <2113ef59-0efd-4de2-83f7-f5940ce40fca@roeck-us.net>
2024-06-22 18:16 ` Mike Rapoport
2024-06-23 0:31 ` Wei Yang
2024-06-21 1:11 ` Wei Yang
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=a2f0efdf-7e77-40f5-b74e-db76a1b284dd@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=paulus@ozlabs.org \
--cc=richard.weiyang@gmail.com \
--cc=rppt@kernel.org \
--cc=tj@kernel.org \
/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