From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Jerome Forissier <jerome@forissier.org>, Will Deacon <will@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
maz@kernel.org
Subject: Re: Kernel v5.2+ on HiKey960?
Date: Tue, 10 Dec 2019 16:26:41 +0000 [thread overview]
Message-ID: <3523c365-62a0-1504-9b99-d5d030e000fd@arm.com> (raw)
In-Reply-To: <740865eb-a993-d1dd-ad2e-84529e2012ee@forissier.org>
Hi Jerome,
On 12/10/19 4:20 PM, Jerome Forissier wrote:
> Now if you check the SHA1 hashes of arch/arm64/kernel/vdso/vdso.o in
> various scenarios:
>
> - v5.4, no ccache:
> b82810f6e9495eb8e787e82b4080654ce4afc30a
> - v5.4, with ccache, built from a clean cache:
> b82810f6e9495eb8e787e82b4080654ce4afc30a
> - v5.1, no ccache:
> 8c09a2f25969e2bf74799d6b3fb52d0fbc3d58a8
> - v5.4, with ccache, after building v5.1 (step 3 above):
> 8c09a2f25969e2bf74799d6b3fb52d0fbc3d58a8
This clearly explains the issue and why you were suspecting the vdso library.
Happy that you figured it out.
--
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-10 16:24 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
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 [this message]
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=3523c365-62a0-1504-9b99-d5d030e000fd@arm.com \
--to=vincenzo.frascino@arm.com \
--cc=catalin.marinas@arm.com \
--cc=jerome@forissier.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=will@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