From: Andrew Pinski <apinski@cavium.com>
To: pinskia@gmail.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Will Deacon <will.deacon@arm.com>
Cc: Andrew Pinski <apinski@cavium.com>
Subject: [PATCHv2 0/4] ARM64: Improve copy_page and copy_template for ThunderX
Date: Tue, 12 Jan 2016 23:08:14 -0800 [thread overview]
Message-ID: <1452668899-3553-1-git-send-email-apinski@cavium.com> (raw)
This is version 2. I expanded it to include copy_template as it was a simple
extension to the new version of the patch.
Changes since v1:
1) Add infastructure for checking MIDR for features
2) Use the copy_page version from Will Deacon
3) Add prefetching feature
4) Add prefetching to copy_page
5) Add prefetching to copy_template
Andrew Pinski (5):
ARM64: Support midr detected cpufeature
ARM64 Improve copy_page for 128 byte cache line
ARM64: Add Needs software prefetching cap
ARM64: Patch in prefetching for copy_page is requested
ARM64: Patch in prefetching in copy_template
arch/arm64/include/asm/cpufeature.h | 29 ++++++++++++++--
arch/arm64/include/asm/cputype.h | 7 ++++
arch/arm64/kernel/cpu_errata.c | 26 --------------
arch/arm64/kernel/cpufeature.c | 27 ++++++++++++++-
arch/arm64/lib/copy_page.S | 64 ++++++++++++++++++++++++++++++----
arch/arm64/lib/copy_template.S | 12 ++++++
arch/arm64/lib/memcpy.S | 2 +
7 files changed, 129 insertions(+), 38 deletions(-)
--
1.7.2.5
next reply other threads:[~2016-01-13 7:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 7:08 Andrew Pinski [this message]
2016-01-13 7:08 ` [PATCH 1/5] ARM64: Support midr detected cpufeature Andrew Pinski
2016-01-13 7:08 ` [PATCH 2/5] ARM64 Improve copy_page for 128 byte cache line Andrew Pinski
2016-01-13 7:08 ` [PATCH 3/5] ARM64: Add Needs software prefetching cap Andrew Pinski
2016-01-13 7:08 ` [PATCH 4/5] ARM64: Patch in prefetching for copy_page is requested Andrew Pinski
2016-01-13 7:08 ` [PATCH 5/5] ARM64: Patch in prefetching in copy_template Andrew Pinski
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=1452668899-3553-1-git-send-email-apinski@cavium.com \
--to=apinski@cavium.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pinskia@gmail.com \
--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
all inboxes | Powered by JetHome®