From: David Hildenbrand <david@redhat.com>
To: "Liang, Liang (Leo)" <Liang.Liang@amd.com>,
Mike Rapoport <rppt@linux.ibm.com>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
amd-gfx list <amd-gfx@lists.freedesktop.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Huang, Ray" <Ray.Huang@amd.com>,
"Koenig, Christian" <Christian.Koenig@amd.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
George Kennedy <george.kennedy@oracle.com>
Subject: Re: slow boot with 7fef431be9c9 ("mm/page_alloc: place pages to tail in __free_pages_core()")
Date: Tue, 16 Mar 2021 09:37:48 +0100 [thread overview]
Message-ID: <0cc972a1-5b40-3017-33f8-b2610489ee18@redhat.com> (raw)
In-Reply-To: <MW3PR12MB453781F0AD49AF3787DE4230F36B9@MW3PR12MB4537.namprd12.prod.outlook.com>
On 16.03.21 09:00, Liang, Liang (Leo) wrote:
> [AMD Public Use]
>
> Hi Mike,
>
> Thanks for help. The patch works for me and boot time back to normal. So it's a fix, or just WA?
Hi Leo,
excluding up to 16 MiB of memory on every system just because that
single platform is weird is not acceptable.
I think we have to figure out
a) why that memory is so special. This is weird.
b) why the platform doesn't indicate it in a special way. Why is it
ordinary system RAM but still *that* slow?
c) how we can reliably identify such memory and exclude it.
I'll have a peek at the memory layout of that machine from boot logs
next to figure out if we can answer any of these questions.
Just to verify: this does happen on multiple machines, not just a single
one? (i.e., we're not dealing with faulty RAM)
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-03-16 8:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 14:41 Deucher, Alexander
2021-03-11 15:02 ` David Hildenbrand
2021-03-12 14:06 ` Deucher, Alexander
2021-03-12 14:12 ` David Hildenbrand
2021-03-12 15:39 ` Deucher, Alexander
2021-03-12 15:48 ` David Hildenbrand
2021-03-12 16:15 ` Deucher, Alexander
2021-03-12 16:19 ` Liang, Liang (Leo)
2021-03-12 16:46 ` David Hildenbrand
2021-03-13 4:04 ` Liang, Liang (Leo)
2021-03-13 9:05 ` David Hildenbrand
2021-03-13 13:48 ` Mike Rapoport
2021-03-15 13:04 ` David Hildenbrand
2021-03-16 0:36 ` Liang, Liang (Leo)
2021-03-16 6:50 ` Mike Rapoport
2021-03-16 8:00 ` Liang, Liang (Leo)
2021-03-16 8:37 ` David Hildenbrand [this message]
2021-03-16 8:43 ` Liang, Liang (Leo)
2021-03-16 8:54 ` David Hildenbrand
2021-03-16 8:58 ` Liang, Liang (Leo)
2021-03-16 9:08 ` David Hildenbrand
2021-03-16 10:30 ` Mike Rapoport
2021-03-16 11:02 ` Liang, Liang (Leo)
2021-03-16 11:10 ` 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=0cc972a1-5b40-3017-33f8-b2610489ee18@redhat.com \
--to=david@redhat.com \
--cc=Alexander.Deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=Liang.Liang@amd.com \
--cc=Ray.Huang@amd.com \
--cc=akpm@linux-foundation.org \
--cc=amd-gfx@lists.freedesktop.org \
--cc=george.kennedy@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rppt@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
all inboxes | Powered by JetHome®