From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Qian Cai <cai@lca.pw>, Will Deacon <will.deacon@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: LTP hugemmap05 test case failure on arm64 with linux-next (next-20190613)
Date: Mon, 17 Jun 2019 07:02:02 +0530 [thread overview]
Message-ID: <054b6532-a867-ec7c-0a72-6a58d4b2723e@arm.com> (raw)
In-Reply-To: <1560514539.5154.20.camel@lca.pw>
Hello Qian,
On 06/14/2019 05:45 PM, Qian Cai wrote:
> On Fri, 2019-06-14 at 11:20 +0100, Will Deacon wrote:
>> Hi Qian,
>>
>> On Thu, Jun 13, 2019 at 05:34:01PM -0400, Qian Cai wrote:
>>> LTP hugemmap05 test case [1] could not exit itself properly and then degrade
>>> the
>>> system performance on arm64 with linux-next (next-20190613). The bisection
>>> so
>>> far indicates,
>>>
>>> BAD: 30bafbc357f1 Merge remote-tracking branch 'arm64/for-next/core'
>>> GOOD: 0c3d124a3043 Merge remote-tracking branch 'arm64-fixes/for-next/fixes'
>>
>> Did you finish the bisection in the end? Also, what config are you using
>> (you usually have something fairly esoteric ;)?
>
> No, it is still running.
>
> https://raw.githubusercontent.com/cailca/linux-mm/master/arm64.config
>
Were you able to bisect the problem till a particular commit ?
- Anshuman
next prev parent reply other threads:[~2019-06-17 1:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 21:34 Qian Cai
2019-06-14 10:20 ` Will Deacon
2019-06-14 12:15 ` Qian Cai
2019-06-17 1:32 ` Anshuman Khandual [this message]
2019-06-17 1:41 ` Qian Cai
2019-06-24 9:35 ` Will Deacon
2019-06-24 12:58 ` Qian Cai
2019-06-24 21:30 ` Qian Cai
2019-06-24 21:53 ` Mike Kravetz
2019-06-27 18:09 ` Mike Kravetz
2019-06-27 18:54 ` Qian Cai
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=054b6532-a867-ec7c-0a72-6a58d4b2723e@arm.com \
--to=anshuman.khandual@arm.com \
--cc=cai@lca.pw \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=will.deacon@arm.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