From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Jerome Forissier <jerome@forissier.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Kernel v5.2+ on HiKey960?
Date: Wed, 4 Dec 2019 12:55:07 +0000 [thread overview]
Message-ID: <a24f817e-86dc-ae32-417d-08eadc96d0eb@arm.com> (raw)
In-Reply-To: <20191204101851.GC13081@arrakis.emea.arm.com>
On 12/4/19 10:18 AM, Catalin Marinas wrote:
>> 1. "arm64: vdso: Substitute gettimeofday() with C implementation"
> Commit 28b1a824a4f4, merged in 5.3
>
>> 2. "arm64: vdso: Explicitly add build-id option"
> Commit 7a0a93c51799, merged in 5.2
>
>> 3. "arm64: arch_timer: Ensure counter register reads occur with seqlock
>> held"
> Commit 75a19a0202db, merged in 5.2.
>
>> 4. "arm64: vdso: Remove stale files from old assembly implementation"
> Commit 37a5076098c1, merged in 5.4.
>
> The above is a pretty random set of reverts that doesn't really help
> pinpoint the issue.
>
> Since 5.2 was the first kernel where the regression was noticed, could
> you try reverting commit 75a19a0202db in 5.2 and try that specific
> kernel version? If this doesn't solve the issue, it may be simpler to
> bisect only between 5.1 and 5.2 rather than across multiple kernel
> versions.
I agree with Catalin here. The unified vDSO change is a 5.3+ change, should not
impact what you are seeing in 5.2.
Could you please as well provide some guidelines to reproduce your scenario
exactly? This would help in the debugging.
--
Regards,
Vincenzo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-04 12:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 15:43 Kernel v5.2+ on HiKey960? Jerome Forissier
2019-12-03 17:47 ` Marc Zyngier
2019-12-04 9:01 ` Jerome Forissier
2019-12-04 10:18 ` Marc Zyngier
2019-12-04 12:22 ` Jerome Forissier
2019-12-04 12:49 ` Vincenzo Frascino
2019-12-04 13:28 ` Jerome Forissier
2019-12-04 10:18 ` Catalin Marinas
2019-12-04 12:55 ` Vincenzo Frascino [this message]
2019-12-04 14:03 ` Jerome Forissier
2019-12-05 12:04 ` Vincenzo Frascino
2019-12-05 14:48 ` Jerome Forissier
2019-12-05 14:59 ` Vincenzo Frascino
2019-12-04 13:15 ` Jerome Forissier
2019-12-04 14:28 ` Catalin Marinas
2019-12-04 14:58 ` Jerome Forissier
2019-12-04 17:57 ` Will Deacon
2019-12-05 7:26 ` Jerome Forissier
2019-12-05 8:57 ` Will Deacon
2019-12-05 14:54 ` Jerome Forissier
2019-12-06 16:09 ` Will Deacon
2019-12-10 16:20 ` Jerome Forissier
2019-12-10 16:26 ` Vincenzo Frascino
2019-12-11 8:57 ` Jerome Forissier
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=a24f817e-86dc-ae32-417d-08eadc96d0eb@arm.com \
--to=vincenzo.frascino@arm.com \
--cc=catalin.marinas@arm.com \
--cc=jerome@forissier.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).