From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] arm64: mm: Fix NOMAP page initialization
Date: Fri, 3 Feb 2017 18:16:27 +0000 [thread overview]
Message-ID: <20170203181626.GL23547@arm.com> (raw)
In-Reply-To: <20170203151414.GE16822@rric.localdomain>
On Fri, Feb 03, 2017 at 04:14:14PM +0100, Robert Richter wrote:
> On 17.01.17 19:16:56, Will Deacon wrote:
> > I can't really see the trend given that, for system time, your
> > pfn_valid_within results have a variance of ~9 and the early_pfn_valid
> > results have a variance of ~92. Given that the variance seems to come
> > about due to the reboots, I think we need more numbers to establish whether
> > the data sets end up largely overlapping or if they really are disjoint.
>
> Assuming the numbers of both versions are not significant, please
> apply one or the other.
I'd rather apply the pfn_valid_within version, but please can you Ack the
patch first, since there was some confusion when it was posted about a
translation fault that was never reproduced.
Thanks,
Will
next prev parent reply other threads:[~2017-02-03 18:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 16:54 [PATCH v3] arm64: mm: Fix NOMAP page initialization Robert Richter
2017-01-04 13:56 ` Ard Biesheuvel
2017-01-05 2:03 ` Hanjun Guo
2017-01-06 1:07 ` Hanjun Guo
2017-01-06 5:22 ` Prakash B
2017-01-09 5:09 ` Hanjun Guo
2017-01-09 6:15 ` Prakash B
2017-01-06 8:37 ` Ard Biesheuvel
2017-01-09 5:14 ` Hanjun Guo
2017-01-09 11:53 ` Robert Richter
2017-01-12 16:05 ` Will Deacon
2017-01-12 18:58 ` Robert Richter
2017-01-13 9:19 ` Will Deacon
2017-01-13 13:15 ` Robert Richter
2017-01-17 10:00 ` Robert Richter
2017-01-17 19:16 ` Will Deacon
2017-02-03 15:14 ` Robert Richter
2017-02-03 18:16 ` Will Deacon [this message]
2017-01-05 11:03 ` Robert Richter
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=20170203181626.GL23547@arm.com \
--to=will.deacon@arm.com \
--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).