From: "bhe@redhat.com" <bhe@redhat.com>
To: Rahul Gopakumar <gopakumarr@vmware.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"natechancellor@gmail.com" <natechancellor@gmail.com>,
"ndesaulniers@google.com" <ndesaulniers@google.com>,
"clang-built-linux@googlegroups.com"
<clang-built-linux@googlegroups.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
Rajender M <manir@vmware.com>, Yiu Cho Lau <lauyiuch@vmware.com>,
Peter Jonasson <pjonasson@vmware.com>,
Venkatesh Rajaram <rajaramv@vmware.com>
Subject: Re: Performance regressions in "boot_time" tests in Linux 5.8 Kernel
Date: Tue, 13 Oct 2020 13:08:24 +0800 [thread overview]
Message-ID: <20201013050824.GK25604@MiWiFi-R3L-srv> (raw)
In-Reply-To: <DM6PR05MB529281F914953691E0F52D1CA4070@DM6PR05MB5292.namprd05.prod.outlook.com>
On 10/12/20 at 05:21pm, Rahul Gopakumar wrote:
> Hi Baoquan,
>
> Attached collected dmesg logs for with and without
> commit after adding memblock=debug to kernel cmdline.
Thanks, I have got the root cause, will make a patch for your testing
soon.
next prev parent reply other threads:[~2020-10-13 5:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 13:15 Rahul Gopakumar
2020-10-10 6:11 ` bhe
2020-10-12 17:21 ` Rahul Gopakumar
2020-10-13 5:08 ` bhe [this message]
2020-10-13 13:17 ` bhe
2020-10-20 13:45 ` Rahul Gopakumar
2020-10-20 15:18 ` bhe
2020-10-20 15:26 ` Rahul Gopakumar
2020-10-22 4:04 ` bhe
2020-10-22 17:21 ` Rahul Gopakumar
2020-11-02 14:15 ` Rahul Gopakumar
2020-11-02 14:30 ` bhe
2020-11-03 12:34 ` Rahul Gopakumar
2020-11-03 14:03 ` bhe
2020-11-12 14:51 ` bhe
2020-11-20 3:11 ` Rahul Gopakumar
2020-11-22 1:08 ` bhe
2020-11-24 15:03 ` Rahul Gopakumar
2020-11-30 16:55 ` Mike Rapoport
2020-12-11 16:16 ` Rahul Gopakumar
2020-12-13 15:15 ` bhe
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=20201013050824.GK25604@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=clang-built-linux@googlegroups.com \
--cc=gopakumarr@vmware.com \
--cc=lauyiuch@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manir@vmware.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=pjonasson@vmware.com \
--cc=rajaramv@vmware.com \
--cc=rostedt@goodmis.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